chore(deps): update dependency @netlify/eslint-config-node to ^3.0.4 #361
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
github-actions
bot
added
the
type: chore
renovate
bot
force-pushed
the
renovate/netlify-eslint-config-node-3.x
branch
from
6619cc9 to
55532f5
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/netlify-eslint-config-node-3.x
branch
from
55532f5 to
445343a
Compare
erezrokah
force-pushed
the
renovate/netlify-eslint-config-node-3.x
branch
2 times, most recently
from
c0c36ab to
445343a
Compare
renovate
bot
force-pushed
the
renovate/netlify-eslint-config-node-3.x
branch
from
445343a to
853a01c
Compare
|
We should see if tests are passing after merging #363 and rebasing |
renovate
bot
force-pushed
the
renovate/netlify-eslint-config-node-3.x
branch
4 times, most recently
from
eaaac4e to
eb1d1c0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/netlify-eslint-config-node-3.x
branch
from
eb1d1c0 to
4a75574
Compare
serhalp
added a commit
that referenced
this pull request
Apr 5, 2024
* chore: run build step before `npm run test` The integration tests require the source to have been built. The e2e tests do as well, but are already running this in a different way. There isn't much of a clean separation of the test config by test type, so I decided to keep it simple by just adding it as a step on a full `npm run test` run. Technically you could still pull down this repo and start running `vitest` and run into this, but that seems rare enough and I'll document this prerequisite in my next commit. * docs(readme): mention prereq for integration tests See previous commit. Ideally we'd fully automate this but it may not be worth the trouble at the moment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.0.1->^3.0.4Release Notes
netlify/eslint-config-node
v3.0.4Compare Source
v3.0.3Compare Source
v3.0.2Compare 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.