[Release automation] Add npm_tag input to the release workflow
#9252
Conversation
This file contains hidden or 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
Collaborator
💚 Build Succeededcc @tkajtoch |
acstll
approved these changes
Dec 5, 2025
Contributor
acstll
left a comment
acstll
left a comment
There was a problem hiding this comment.
🟢 Checked yml is correct (did an extra check with AI), looked for typos and tested the script bits manually as well.
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.
Summary
Resolves https://github.com/elastic/eui-private/issues/469
This adds the
npm_taginput to our new release workflow to allow creating backport releases. Documentation will be added to our wiki separately.Why are we making this change?
We need this to create backport releases of EUI packages.
Screenshots #
Impact to users
No impact to end users
QA