Skip to content

ci: expand NEW_RELEASE_VERSION in the publish step - #1776

Merged
madhavilosetty-intel merged 1 commit into
mainfrom
ci/fix-publish-version-substitution
Jul 27, 2026
Merged

ci: expand NEW_RELEASE_VERSION in the publish step#1776
madhavilosetty-intel merged 1 commit into
mainfrom
ci/fix-publish-version-substitution

Conversation

@madhavilosetty-intel

Copy link
Copy Markdown
Contributor

PR Checklist

  • Unit Tests have been added for new changes
  • API tests have been updated if applicable
  • All commented code has been removed
  • If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?

If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the release workflow so the NEW_RELEASE_VERSION environment variable is expanded when rewriting dist/package.json during the publish job, ensuring the published package has the correct semantic-release version.

Changes:

  • Fix shell quoting in the sed command so NEW_RELEASE_VERSION is interpolated into the version field before npm publish.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@madhavilosetty-intel
madhavilosetty-intel merged commit 3faadb3 into main Jul 27, 2026
7 checks passed
@madhavilosetty-intel
madhavilosetty-intel deleted the ci/fix-publish-version-substitution branch July 27, 2026 22:55
@RosieAMT

Copy link
Copy Markdown

🎉 This PR is included in version 3.3.19 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants