Open
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.0 to 4.1.1. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.0...4.1.1) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.1.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
commit: |
aarond-sp
added a commit
to aarond-sp/conventional-changelog
that referenced
this pull request
Feb 4, 2026
The parserOpts parameter (including issuePrefixes) was being received but not passed correctly to the generators. This caused custom options configured via parserOpts to be ignored since v10.0.2. Changes: - Pass parserOpts as second argument to generator.commits() in the conventionalChangelog wrapper function - Pass parserOpts to Bumper.commits() even when commitsOpts is not set - Add test to verify custom issuePrefixes are applied correctly Note: The angular preset's writer template hardcodes '#' as the issue prefix in the output, so XYZ-123 will be parsed correctly but displayed as release-it#123. Users who want to preserve the original prefix in output need to customize writerOpts. Fixes release-it#133
aarond-sp
added a commit
to aarond-sp/conventional-changelog
that referenced
this pull request
Feb 4, 2026
The parserOpts parameter (including issuePrefixes) was being received but not passed correctly to the generators. This caused custom options configured via parserOpts to be ignored since v10.0.2. Changes: - Pass parserOpts as second argument to generator.commits() in the conventionalChangelog wrapper function - Pass parserOpts to Bumper.commits() even when commitsOpts is not set - Add test to verify custom issuePrefixes are applied correctly - Fix test setup to disable GPG tag signing (for envs with gpgSign=true) Note: The angular preset's writer template hardcodes '#' as the issue prefix in the output, so XYZ-123 will be parsed correctly but displayed as release-it#123. Users who want to preserve the original prefix in output need to customize writerOpts. Fixes release-it#133
webpro
pushed a commit
that referenced
this pull request
Feb 5, 2026
* fix: pass parserOpts to both Bumper and ConventionalChangelog The parserOpts parameter (including issuePrefixes) was being received but not passed correctly to the generators. This caused custom options configured via parserOpts to be ignored since v10.0.2. Changes: - Pass parserOpts as second argument to generator.commits() in the conventionalChangelog wrapper function - Pass parserOpts to Bumper.commits() even when commitsOpts is not set - Add test to verify custom issuePrefixes are applied correctly - Fix test setup to disable GPG tag signing (for envs with gpgSign=true) Note: The angular preset's writer template hardcodes '#' as the issue prefix in the output, so XYZ-123 will be parsed correctly but displayed as #123. Users who want to preserve the original prefix in output need to customize writerOpts. Fixes #133 * fix(test): use cross-platform multi-line commit syntax Use multiple -m flags instead of embedded newlines for Git commit messages, which fixes test failures on Windows where shell commands don't properly handle literal newlines.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps js-yaml from 4.1.0 to 4.1.1.
Changelog
Sourced from js-yaml's changelog.
Commits
cc482e74.1.1 released50968b8dist rebuildd092d86lint fix383665ffix prototype pollution in merge (<<)0d3ca7aREADME.md: HTTP => HTTPS (#678)49baadddoc: 'empty' style option for !!nullba3460eFix demo link (#618)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.