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
Doesn't GHA update the major version number when there are breaking changes? Is it really "best practice" to use a full version tag, which means that when minor versions or patches are published, they won't be automatically used.
"Recommendation: bind to major versions to get functionality and fixes but reserve binding to a specific release or SHA as a mitigation strategy for unforeseen breaks."
which seems to apply here as well.
The text was updated successfully, but these errors were encountered:
What are the current best practice guidelines for specifying the version of github-action to use?
https://docs.cypress.io/guides/continuous-integration/github-actions#Explicit-Version-Number shows:
whereas https://github.com/cypress-io/github-action#explicit-version is not so outspoken about using a full version tag:
Doesn't GHA update the major version number when there are breaking changes? Is it really "best practice" to use a full version tag, which means that when minor versions or patches are published, they won't be automatically used.
In any case, the document https://docs.cypress.io/guides/continuous-integration/github-actions should be updated to align with PR #668 which updates to v5.
See also guidance in GitHub Actions toolkit
"Recommendation: bind to major versions to get functionality and fixes but reserve binding to a specific release or SHA as a mitigation strategy for unforeseen breaks."
which seems to apply here as well.
The text was updated successfully, but these errors were encountered: