Skip to content

chore(deps): bump systemfsoftware/pnpm-release-management/.github/workflows/release.yml from 9615867c17489fb04be8bc74f568659d687df612 to 1e897828d917341fb7dd444c7bbd6cfa0998caa9 - #144

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/systemfsoftware/pnpm-release-management/dot-github/workflows/release.yml-1e897828d917341fb7dd444c7bbd6cfa0998caa9
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/systemfsoftware/pnpm-release-management/dot-github/workflows/release.yml-1e897828d917341fb7dd444c7bbd6cfa0998caa9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps systemfsoftware/pnpm-release-management/.github/workflows/release.yml from 9615867c17489fb04be8bc74f568659d687df612 to 1e897828d917341fb7dd444c7bbd6cfa0998caa9.

Changelog

Sourced from systemfsoftware/pnpm-release-management/.github/workflows/release.yml's changelog.

Changelog

1.0.0

  • version-management bump now creates changelogDir before parking a moved member's changelog there. A fresh checkout has no such directory, so under registry changelog storage (the default) bump used to refuse with ChangelogUnwritable ... reason=NotFound as soon as an intent moved a member. A changelogDir path that holds a regular file is still refused with ChangelogUnwritable.
  • bump now writes each moved member's changelog where versioning.changelog.storage says it lives. Under repository the member's own changelog gains a ## <version> section above its earlier sections, below any title or preamble, in the file's line endings. The file is created when absent, a changelog that already has the version is left as it is, and nothing is parked, so the release phase finds the notes it reads. Under registry or unset, bump parks one file per moved member under changelogDir, byte for byte as before. Breaking for adapter authors: MemberChangelogEntry carries storage and path instead of changelogDir, and BumpCommand requires changelogStorage. memberChangelogPathOf, withVersionSection and releaseNotesOf are now exported from @systemfsoftware/release-language.
  • Under the turbo gate strategy, change evidence now fetches the @turbo/<os>-<arch> package the lockfile pins, from the lockfile's tarball URL or the public npm registry. It checks the bytes against the recorded integrity, requires the binary to print the pinned version, and runs it with telemetry off. A verdict needs no installed workspace, only that registry. Breaking for adapter authors: ChangeEvidenceLive requires an HttpClient; provide one such as FetchHttpClient.layer. Install-bound refusal details become fetch-bound ones under the unchanged turbo pin unusable: stem: no published binary, no recorded integrity, an unfetchable tarball, mismatched bytes, no bin/turbo, or a version other than the pin. A failed dry run names turbo (<package>@<pin>).
  • versioning.strategy is now "changesets" in place of "pnpm", and a config that still sets "pnpm" no longer decodes. Change it to "changesets". version bump versions each package from its intents, bumps dependents, writes per-package changelogs and keeps exact inner pins.
  • When pnpm cannot be started, the release tools now report pnpm could not be started: ENOENT (...) instead of manifest-unreadable at the repository root. A manifest that really cannot be read is still reported as ManifestUnreadable at its path. Breaking for adapter authors: MemberRefusal gains CommandUnstartable { command, reason }, so exhaustive matches over it need a new case.
  • changeset check now lists a package deleted on the head as deleted instead of failing with "cannot read". A deleted package needs no intent. ChangeEvidence gains a deleted list of package names.
  • The release no longer fetches versions from an npm registry or compares packed bytes. Packages ship through the Nix registry, which is content-addressed, so release plan and release tag decide only from changesets and tags: a version whose tag exists is skipped, never republished. A catalog bump that rewrites a packed package.json no longer blocks a release. Removed: release adopt, --tarballs on release plan and release tag, the release ledger (release-ledger.json) and its append-only check in changeset check, and the tag-integrity-mismatch, integrity-*, tarball-*, ledger-*, version-burned, version-intent-malformed, version-unknown-package and tag-annotation-* refusals. release tag still writes annotated tags, but the message is the tag name and nothing reads it back. The packages @systemfsoftware/adoption-adapter and @systemfsoftware/tarball-adapter are deleted. Breaking for engine callers: planCell and tagCell no longer require TarballPort or LedgerPort, PlanRequest and TagRequest have no tarballs, and the exported adoption and integrity symbols, RegistryPort, LedgerPort, TarballPort and GitPort.tagAnnotation are gone. ChangeEvidenceLive requires an HttpClient instead of RegistryPort. Breaking for workflow callers: drop --tarballs and release adopt from any script. release.yml no longer builds .#workspace-tarballs, so a caller needs no such flake output for the release.
  • The release config accepts legacyTags: { tag, through } for releases cut under another tag scheme, such as a bare v{version}. A version at or below through whose legacy tag points at a commit declaring that exact version counts as released, so release plan and release tag no longer owe a second <name>@v<version> tag for it, and release plan prints legacy release <tag> (<name>@<version>) for each such version. A legacy tag whose commit declares a different version, or no such package, is refused with legacy-tag-unverified. Breaking for engine callers: the plan, tag and GitHub release cells can fail with a new LegacyTagUnverified refusal, so exhaustive matches over their failures need that case, and PlanReport gains a required legacy list.
  • version-management bump keeps each intent a separate block in a member changelog, with a blank line between intents, instead of joining their markdown with a space. A list in one intent no longer fuses into the paragraph before it, so the changelog passes the repository's own dprint check.
  • github-release-management pr now opens the release PR from the tree version-management bump left. Changes to tracked files open or refresh it, and an unchanged tree closes it. Before, pr counted intents bump had already consumed, reported "nothing to release" and exited 0. pr no longer bumps by itself, and refuses with PullRequestUnversioned while an intent is still on disk. The release commit holds only tracked changes and the changelogs bump created, so an untracked artifact in the checkout no longer lands in the release PR. Breaking for adapter authors: GitPort gains trackedChanges, and commitAll becomes commitRelease(message, created). PullRequestRefusal adds PullRequestUnversioned and PullRequestTreeUnreadable. PullRequestCommand requires changes and created; PullRequestRequest requires changelogDir.
  • github-release-management pr now commits the release as github-actions[bot], so it works on a runner with no git identity configured. Before, the commit failed there and pr printed cannot read body file: git:commit. A failed git command in pr now reports the command and the error git printed, instead of a body-file or pull-request-head error. Breaking for adapter authors: PullRequestRefusal gains PullRequestGitFailed { command, stderr }.
  • pr now finds only the open pull request whose head is the release branch in the repository's own owner. It used to treat the first open pull request in the repository as the release PR, because GitHub ignores a head filter that is not written as owner:branch, so a repository with any other open pull request had that one renamed, its body replaced, or closed. Now a repository with no release PR gets a new one, and every other pull request is left as it is.
  • version-management bump writes each root-changelog bullet as a top-level list item, - <summary>, instead of indenting it by two spaces. The release pull request it opens now passes the repository's own dprint check.
  • github-release-management tag now writes each annotated release tag as github-actions[bot], so it works on a runner with no git identity configured. Before, git tag -a failed there with "Committer identity unknown" and tag printed cannot read captured file: git:write-tag. tag now pushes only the captured tags the remote doesn't have yet. A captured tag already on the remote at the release commit is left alone, so re-running tag after a partial push finishes the set. A captured tag already on the remote at another commit refuses the run with tag-at-other-commit, naming the tag and both commits, and nothing is pushed. Breaking for adapter authors: tagCell can fail with TagAtOtherCommit { tag, expected, found }.
  • A failed git command while tagging now reports the command and the error git printed, instead of cannot read captured file: git:push-tags. Breaking for adapter authors: TagRefusal gains TagGitFailed { command, stderr }, so exhaustive matches over it need a new case.
  • changeset-management check with "gate": { "strategy": "paths" } now refuses in a repository whose root keeps a Turbo config at both the comparison base and the head, printing a paths gate refused: line that names the config and the fix: "gate": { "strategy": "turbo" }. A pull request that adds or removes the Turbo config is still decided by paths. Breaking for adapter authors: EvidenceRefusal gains PathsGateUnderTurbo { turboConfig }, so exhaustive matches over it need a new case.
  • version-management bump versions a changesets workspace whose private root package.json has no version. It no longer reads the root manifest under changesets, so it stops refusing with VersionIntentMalformed: path=package.json.
Commits
  • 1e89782 ci(release): reconcile in the plan job (#121)
  • b9ff6af fix(changesets-adapter): rewrite sibling ranges only where they use the works...
  • cf65dc1 fix(release): every caller grants id-token, since GitHub checks the publish j...
  • e55fd25 fix(release): reconcile the release PR from the default branch's head on ever...
  • 6008c7d chore: enrol every compound pack from systemfsoftware main (#117)
  • ac6661d fix(npm-trust): count a package as trusted only on an exact repository and fi...
  • See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

…kflows/release.yml

Bumps [systemfsoftware/pnpm-release-management/.github/workflows/release.yml](https://github.com/systemfsoftware/pnpm-release-management) from 9615867c17489fb04be8bc74f568659d687df612 to 1e897828d917341fb7dd444c7bbd6cfa0998caa9.
- [Changelog](https://github.com/systemfsoftware/pnpm-release-management/blob/main/CHANGELOG.md)
- [Commits](systemfsoftware/pnpm-release-management@9615867...1e89782)

---
updated-dependencies:
- dependency-name: systemfsoftware/pnpm-release-management/.github/workflows/release.yml
  dependency-version: 1e897828d917341fb7dd444c7bbd6cfa0998caa9
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: automerge. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

This branch has not been deployed

No deployments
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.

0 participants