Skip to content
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

Feature Request: Align semver with the updatecli version #829

Open
v1v opened this issue Nov 19, 2024 · 0 comments
Open

Feature Request: Align semver with the updatecli version #829

v1v opened this issue Nov 19, 2024 · 0 comments

Comments

@v1v
Copy link
Contributor

v1v commented Nov 19, 2024

Is your feature request related to a problem?

I've found a bit tedious to know what changes are coming from the latest updatecli version when using this action.

For instance:

  1. https://github.com/elastic/oblt-actions/releases/tag/v1.22.1 is our meta-project to store some everyday GH composite actions.
  2. build(deps): bump the github-actions group across 7 directories with 2 updates elastic/oblt-actions#159 was a bump

Then, I went through the changelog at https://github.com/updatecli/updatecli-action/releases to determine the former and new versions, and then I dived into #568 and similar changes.

My issue was regarding https://github.com/updatecli/updatecli/releases/tag/v0.86.0, which contains a breaking change.

Unfortunately, I could not find version v2.71.0 or previous ones in https://github.com/updatecli/updatecli-action, which contained a breaking change.it

Solution you'd like

I want to make the version at https://github.com/updatecli/updatecli to match the version at https://github.com/updatecli/updatecli-actions.

I understand there might be some edge cases:

  1. What if a patch is needed in https://github.com/updatecli/updatecli-actions?
  2. What if a breaking change is needed in https://github.com/updatecli/updatecli-action?

For such, I think we can use five digits server

major-updatecli-action.minor-updatecli-action.major-updatecli.minor-updatecli.patch-updatecli

Therefore, a breaking change in the updatecli-action could be:

  1. renamed input
  2. changed runner support

Otherwise, everything else is a minor bump.

For instance, today, we could use 3.0.0.86.1, then if a new udpatecli version then 3.0.0.87.0...

If a new change in the updatecli-action then, 3.1.0.87.0

Alternatives you've considered

I know I could pin the version using the input version, however if I do so, I need to then update it somehow.

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant