Skip to content

Added code for npm publishing via semantic release.#15

Open
dlabaj wants to merge 2 commits intomainfrom
ci-npm-updates
Open

Added code for npm publishing via semantic release.#15
dlabaj wants to merge 2 commits intomainfrom
ci-npm-updates

Conversation

@dlabaj
Copy link
Contributor

@dlabaj dlabaj commented Feb 25, 2026

Added code to perform npm publish for the cli repo via semantic release. Close issue #14

@dlabaj dlabaj changed the title Added code for npm publishing. Added code for npm publishing via semantic release. Feb 25, 2026
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "lts/*"

Choose a reason for hiding this comment

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

curious why you went with this here instead of 20?

"@semantic-release/github"
],
"dryRun": true
}

Choose a reason for hiding this comment

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

this file will need some changes if we want to have the standard releases be -prerelease like in our other repos, but if we don't care about that ignore this comment.

Comment on lines +25 to +26
"assets": ["CHANGELOG.md", "package.json"],
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"

Choose a reason for hiding this comment

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

I'm curious what prompted you to add these release commits, but that isn't to say I'm against it.

@@ -1,2 +1,2 @@
{
"name": "patternfly-cli",

Choose a reason for hiding this comment

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

Also do you want to change this to @patternfly/patternfly-cli so that it releases under the PF npm org?

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

Successfully merging this pull request may close these issues.

2 participants