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
I and my teammates have wasted a significant number of hours tracking down why things have broken, only to realize there’s been a significant change to the behavior of this action, with no major version bump.
The text was updated successfully, but these errors were encountered:
made v4 print a deprecation message for 2..4 weeks
disabled v4
Also keep in mind, hidden files in Linux are widely used for settings, but barely hold any secret information. There is almost no security risk to these files, especially as we're talking about Git repositories with local editor or tool configs. Also dot-files are usually not created in a CI job; the pre-exist in the repository itself. Thus, if these files contain secrets, the secret was already exposed by sharing the files in a repository itself.
In my opinion, this was a complete overreaction by GitHub without understanding the problem and the implications.
What would you like to be added?
Please follow semantic versioning.
If the public API is changed, it must not be distributed as a minor release.
Why is this needed?
For three months in a row now, there have been breaking changes to the public API of this action that were distributed as a minor release.
I and my teammates have wasted a significant number of hours tracking down why things have broken, only to realize there’s been a significant change to the behavior of this action, with no major version bump.
The text was updated successfully, but these errors were encountered: