Skip to content

Tags: codfish/actions

Tags

v3

Toggle v3's commit message
Update v3 tag

v3.3.2

Toggle v3.3.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #59 from codfish/feat/eslint-update

chore: upgrade eslint

v3.3.1

Toggle v3.3.1's commit message
fix: add npm token to sem release action

v3.3.0

Toggle v3.3.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
feat(npm-publish-pr): add dev input and multi-package-manager install…

… syntax in PR comment (#56)

- Add boolean input  for dev dependency install syntax (e.g. npm install -D)
- Show pnpm, npm, yarn, and bun install commands in success comment (pnpm, npm, yarn, bun order)

v3.2.6

Toggle v3.2.6's commit message
fix(release): patch major tag instead of trying to POST

v3.2.5

Toggle v3.2.5's commit message
fix(release): use correct output for updating major tag

v3.2.4

Toggle v3.2.4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix(npm-publish-pr): create npmrc so auth works for token mode (#55)

v3.2.3

Toggle v3.2.3's commit message
fix: fix credentials in workflows

v3.2.2

Toggle v3.2.2's commit message
fix: update release workflow to properly expose semantic outputs

v3.2.1

Toggle v3.2.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: make registry-url optional to avoid conflicts with semantic-rele…

…ase (#48)

Previously, registry-url was hardcoded to 'https://registry.npmjs.org/'
which could conflict with semantic-release's npm authentication.

Changes:
- Made registry-url an optional input parameter (defaults to not set)
- When not provided, no .npmrc authentication is configured
- Added comprehensive documentation on when to use (or not use) this parameter

This allows users to:
- Skip registry-url when using semantic-release (recommended)
- Skip registry-url when only installing dependencies (most common use case)
- Explicitly set registry-url when needed for manual npm publish workflows

See semantic-release docs for more context:
https://semantic-release.gitbook.io/semantic-release/recipes/ci-configurations/github-actions#important-avoid-registry-url-in-setup-node