fix(ci): correct release-please changelog-path to unblock release flow#2045
Merged
codecapitano merged 1 commit intomainfrom May 8, 2026
Merged
fix(ci): correct release-please changelog-path to unblock release flow#2045codecapitano merged 1 commit intomainfrom
codecapitano merged 1 commit intomainfrom
Conversation
The Release please workflow has been failing on every push to main since PR #2023 with: 'illegal pathing characters in path: packages/core/../../CHANGELOG.md'. release-please v17 rejects '..' segments in per-package changelog-path. Move the changelog declaration to a top-level changelog-path resolved from the repo root, drop the per-package overrides, and tighten the linked-versions plugin to silence the 'Multiple paths for ___' warnings. Closes #2044
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes the failing Release please workflow by updating release-please-config.json to avoid disallowed .. segments in changelog-path, while keeping the intended single root changelog behavior.
Changes:
- Set a top-level
changelog-path: "CHANGELOG.md"and remove per-package../../CHANGELOG.mdoverrides. - Simplify the
linked-versionsplugin configuration to only specifygroupName: "faro".
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
codecapitano
added
the
github_actions
kpelelis
approved these changes
May 8, 2026
3 tasks
codecapitano
added a commit
that referenced
this pull request
May 8, 2026
The auto-generated 2.6.0 section listed every conventional commit since the dawn of the repo, because the v2.5.0 git tag points at a dangling commit (be77424) that was never merged into main, and release-please could not anchor the changelog walk on it. Replace the 60+ entries with the two real user-facing changes that landed after v2.5.0: - #2014 — feat(web-sdk): httpHost on performance.resource events - #2015 — feat(replay): pause recording after user inactivity CI/release-please plumbing PRs (#2045, #2048, #2049, #2051, #2053) and dep bumps (#2030, #2031, #2040, #2041) are intentionally omitted \u2014 they have no user-visible impact. Format matches the existing 2.5.0 / 2.4.0 entry style so markdownlint passes without per-line URL wrapping issues. The next release-please run will anchor on this PR's merge commit, so subsequent release PRs will not have this problem.
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.
Why
The
Release pleaseworkflow has been failing on every push tomainsince PR #2023 introduced release-please.Failing run: https://github.com/grafana/faro-web-sdk/actions/runs/25482676993/job/75002074144
release-please v17 rejects
..segments in per-packagechangelog-path. The current config sets"changelog-path": "../../CHANGELOG.md"on each of the 6 packages to point at a single root changelog, which trips the path validator and aborts the run before the release PR is built.What
Single-file change in
release-please-config.json:"changelog-path": "CHANGELOG.md"(resolved from the repo root, no..). All packages now write into the single rootCHANGELOG.md, preserving the original intent."changelog-path": "../../CHANGELOG.md"overrides.linked-versionsplugin to{ "type": "linked-versions", "groupName": "faro" }. The previous explicitcomponentsarray produced harmless but noisy⚠ Multiple paths for ___warnings; the plugin already links every package in thepackagesmap by default.No changes to the workflow, manifest, or
deployment_toolsVault/GitHub App config — the failing run shows token mint, Vault auth, and API access all working end-to-end. The failure is config-only.After this lands, the next push to
mainwill trigger the workflow with the corrected config; release-please walks fromv2.5.0toHEADand should open its first release PR (likelychore(main): release ...).Links
Closes #2044
Checklist