* fix: conditionally append NPM_TOKEN to .npmrc for trusted publishing support
The .npmrc generation now intelligently handles both traditional NPM token
authentication and trusted publishing scenarios:
- Only appends auth token to .npmrc when NPM_TOKEN is defined (not undefined)
- Uses strict comparison (!== undefined) instead of truthy checks
- Provides informative logging when no NPM_TOKEN is present
- Maintains full backward compatibility with existing workflows
This fixes issues with trusted publishing where OIDC tokens from GitHub
Actions are used instead of NPM_TOKEN, preventing 'undefined' from being
written to the registry auth configuration.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Update src/index.ts
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* simplify
* tweak changeset
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* Migrate to ESM
* just use `require.resolve`
* reuse setup action
* checkout PR head for a sec
* ls things
* try a thing
* the dirname had a trailing whitespace, lol
* fix: use latest ghcommit and fix cwd for git-cli
- `cwd` was not working correctly when commitMode was set to `git-cli`,
as it was attempting to resolve the `cwd` twice.
(This problem only occured when specifying a relative path for `cwd`.)
- Update `ghcommit`, and avoid calling `process.chdir()` to change the
working directory. Instead, we now pass the `cwd` option everywhere.
fixes#475
* simplify
* Apply suggestions from code review
---------
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* Fix PRs sometimes not getting reopened
There was a race-condition that means sometimes
existing PRs would not be found,
and new PRs would be opened.
This has now been fixed by fetching existing PRs
before making any changes.
fixes#487
* Apply suggestions from code review
---------
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* Make git add work consistently with subdirectories
Currently, depending on your `commitMode`,
when running the action with `cwd` set to a subdirectory of a repo,
the action will either:
- `git-cli`: add the files changed in the subdirectory only
- `github-api`: add files changed anywhere in the repository
This commit brings github-api in line with git-cli,
so that it only adds files in the current working directory.
* Explicitly set `cwd` for all exec calls
* Avoid using `ExecOptions` from `@actions/exec`
* Rename type
* remove redundant `filter`
---------
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* Create tags on GitHub using API
To allow for signed tags to be created,
rather than use the git CLI to push tags,
manually push each tag using the GitHub API,
which will sign the tag using the built-in GitHub GPG key.
* Use ghcommit to push changes
To allow for all commits to be signed,
use the GitHub API to push changes.
* Add changeset version
* Allow tag publish to fail, assume it was manually published
* Add to changeset
* Update @s0/ghcommit
* Update ghcommit to fix missing ref bug
* Make using GitHub API Optional
Change this to a minor version bump,
with a new feature that allows for using the
GitHub API to create tags and commits.
* Use a strategy pattern for GitHub API vs CLI usage
* refactor git interactions
* fix mock thing
* usechangesets pkg
* switch to `commitMode`
---------
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* Switch to pull request list API instead of search
To reduce the amount of rate-limit that we use,
switch to a cheaper API for determining whether
an existing PR exists for a given branch.
* Ensure PR remains open when updating description
* Update .changeset/clean-bees-count.md
Co-authored-by: willo-icon <161356817+willo-icon@users.noreply.github.com>
---------
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: willo-icon <161356817+willo-icon@users.noreply.github.com>
* Don't create a PR if all changesets are empty
Fixes#205.
Note that this maintains the previous behavior that if there are any
changesets (even empty ones), the action does not publish packages.
* Create three-needles-protect.md
* Update .changeset/three-needles-protect.md
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* fix: body max length
* docs: improve logs
* docs: changeset
* refactor: changeset message to omit some info if message exceeds size limit
* refactor: minor adjustments based on feedback
* Apply nits from code review
* Fixed tests
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* feat: add cwd for projects that not in the root directory
* docs: add cwd to README
* reword the added log
* tweak changeset
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
* Switch to Changesets-based release process
* Bump version
* drop unused variable
* Update .github/workflows/version-or-publish.yml
Co-authored-by: Nicola Molinari <nicola.molinari@commercetools.com>
* Push also to a release line branch when releasing
* Change node version used in the version-or-publish workflow
* Switch to using the local action
Co-authored-by: Nicola Molinari <nicola.molinari@commercetools.com>
* build the action before trying to use it the workflow
* Add changeset and actually setup Changesets, lol
Co-authored-by: Nicola Molinari <nicola.molinari@commercetools.com>
