Skip to content

chore(deps): update dependency @netlify/eslint-config-node to ^2.6.9 #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 17, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 17, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@netlify/eslint-config-node ^2.6.7 -> ^2.6.9 age adoption passing confidence

Release Notes

netlify/eslint-config-node

v2.6.9

Compare Source

v2.6.8

Compare Source


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@github-actions github-actions bot added the type: chore work needed to keep the product and development running smoothly label May 17, 2021
@renovate renovate bot merged commit c4db1ea into main May 17, 2021
@renovate renovate bot deleted the renovate/netlify-eslint-config-node-2.x branch May 17, 2021 14:02
serhalp pushed a commit that referenced this pull request Apr 5, 2024
* ci: run tests against different versions

* ci: ignore lockfiles for pnpm in fixtures

* chore: allow manual trigger

* chore: install next version in e2e

* chore: log install command

* chore: use matrix for unit and integration tests

* chore: patch package.jsons

* chore: add fixture dep

* chore: handle errors in patching

* chore: allow fixtures and tests to exclude versions

* chore: update output syntax

* chore: check version in integration tests too

* chore: update actions

* chore: handle errors reading package.json

* chore: don't patch inside node_modules

* chore: add doc

* chore: allow setting site id

* chore: fix pnpm test

* chore: artifact name

* chore: make stream test conditional

* chore: format with prettier

* chore: fixes and logging for prepare script

* chore: shard e2e tests

* chore: merge reports

* chore: correct reporter

* chore: handle more version constraints

* test: hacky mocking for request-context leak test to work with dynamic import and require

* test: provide NEXT_VERSION env var also to vitest execution step so smoke tests update next versions as well

* test: don't rely on pnpm-lock.yaml to decide on package-manager

* test: handle packageManager field not being set

* test: drop commented out debug code

* revert pnpm-lock.yaml changes

* test: allow updating pnpm lock in vitest fixtures

* test: use --force on vitest tests with pnpm

* test: revert changing integration fixture pnpm command

* test: use actual resolved next version to calculate fixture cache key

* test: don't revert version, otherwise pnpm lock won't match and if you run against non default NEXT_VERSION some mess in working dir seems acceptable to make things work

* test: mock requests instead of spinning actual http server because 13.5.1 doesn't seem to allow overwriting env vars on execution, so we can't change fetch target dynamically

* don't install repo dependencies via pnpm, we use npm for that

* chore: format with prettier

* actually don't use custom pnpm action at all, we are updating dependencies so pnpm locks are not to be trusted for caching

* separate playwright reports for each next version

* fix blob report path ?

---------

Co-authored-by: ascorbic <[email protected]>
Co-authored-by: Michal Piechowiak <[email protected]>
Co-authored-by: pieh <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: chore work needed to keep the product and development running smoothly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant