Skip to content

fix: release workflow without npm token#33

Merged
bastianjakobi merged 1 commit intoonecx:mainfrom
yulmelcorp:fix/npm-release-workflow-fix
Apr 16, 2026
Merged

fix: release workflow without npm token#33
bastianjakobi merged 1 commit intoonecx:mainfrom
yulmelcorp:fix/npm-release-workflow-fix

Conversation

@yulmelcorp
Copy link
Copy Markdown
Contributor

  • release to npm with OIDC as in libs repository

Copy link
Copy Markdown

@mholzaepfel mholzaepfel left a comment

Choose a reason for hiding this comment

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

Looks good to me.
The release.yml file is aligned with the portal-libs setup.
release.config.js looks good as well.
@semantic-release/npm is not included in the libs’ release.config.js, and the exec publish command has been added instead.

@bastianjakobi bastianjakobi self-assigned this Apr 16, 2026
Comment thread release.config.js
@bastianjakobi bastianjakobi merged commit 11188c9 into onecx:main Apr 16, 2026
1 check passed
tkit-dev pushed a commit that referenced this pull request Apr 16, 2026
## [1.7.1](v1.7.0...v1.7.1) (2026-04-16)

### Bug Fixes

* release workflow without npm token ([#33](#33)) ([11188c9](11188c9))
* remove private setting from package.json to reenable release ([#30](#30)) ([2afa37f](2afa37f))
* switch to latest node LTS ([#32](#32)) ([0a54c42](0a54c42))
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.

3 participants