You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, the addition of the version numbers (other than the major version) is a bit unexpected, since GitHub's own docs always use @v1 / @v2 / etc - thus staying on an automatic update of minor/patch versions. This would be my preferred behaviour too. Here's an issue that reports it: #2304
The text was updated successfully, but these errors were encountered:
@peaceiris I do not see #2304 as being a duplicate; it's more of a feature request for a different way to manage dependencies, where this is more of a bug.
Dependabot seems to bump some GitHub Actions to their pre-release versions, notably
setup-node
.Package manager/ecosystem
github_actions
Manifest contents prior to update
Workflow file
Relevant YAML:
Updated dependency
nihalgonsalves/node-typescript-eslint-template#181
What you expected to see, versus what you actually saw
v1.4.4
, the latest release herev2.1.2 (beta)
, the pre-release hereImages of the diff or a link to the PR, issue or logs
Dependabot config
PR by Dependabot: Bump actions/setup-node from v1 to v2.1.2 nihalgonsalves/node-typescript-eslint-template#181
Other info
Additionally, the addition of the version numbers (other than the major version) is a bit unexpected, since GitHub's own docs always use
@v1
/@v2
/ etc - thus staying on an automatic update of minor/patch versions. This would be my preferred behaviour too. Here's an issue that reports it: #2304The text was updated successfully, but these errors were encountered: