Skip to content

fix: lockfile integrity check excludes workspace-local packages - #1044

Merged
bradygaster merged 1 commit into
mainfrom
squad/fix-publish-lockfile-check
Apr 25, 2026
Merged

bradygaster merged 1 commit into
mainfrom
squad/fix-publish-lockfile-check

Conversation

@bradygaster

Copy link
Copy Markdown
Collaborator

The integrity hash validation in squad-npm-publish.yml only excluded file:-prefixed resolved paths, but npm workspaces use bare relative paths (e.g. packages/squad-sdk). Changed to only check integrity for registry-resolved (https://) packages.

This unblocks the v0.9.4 publish workflow.

Closes #0

The integrity hash validation in squad-npm-publish.yml only excluded
file:-prefixed resolved paths, but npm workspaces use bare relative
paths (e.g. packages/squad-sdk). Changed to only check integrity for
registry-resolved (https://) packages.

Closes #0

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bradygaster
bradygaster merged commit b48bd94 into main Apr 25, 2026
12 checks passed
bradygaster added a commit that referenced this pull request Apr 25, 2026
Adds battle-tested knowledge from the v0.9.4 release session:
- GITHUB_TOKEN event propagation limitation and manual workaround
- Root package.json must match sub-package versions
- CHANGELOG.md version entry validation gate
- Lockfile integrity check workspace package handling
- Prebuild version bump local dev fix

PRs #1042, #1043, #1044 cited as source evidence.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bradygaster
bradygaster deleted the squad/fix-publish-lockfile-check branch August 8, 2026 08:43
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.

1 participant