Repository navigation
chore: remove org-enforced workflows and bump next to 16.4.2 - #48
Merged
Merged
Conversation
These checks now run via the org-wide required workflows in labd/.github-workflows.
next 16.4.0 is affected by two critical advisories (GHSA-2464-fhr4-w9xw, GHSA-673q-mjm6-r5xr), which makes the pnpm audit step in CI fail.
Move the .npmrc settings to pnpm-workspace.yaml.
mvantellingen
force-pushed
the
remove-org-enforced-workflows
branch
from
October 25, 2026 18:59
a274fb6 to
49677c3
Compare
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.
Removes the repo-local pinact, zizmor and other security workflows. These checks now run as org-wide required workflows from
labd/.github-workflows, so keeping copies in this repo would only run them twice.CI fixes
pnpm audit --audit-level=criticalfailed on two critical advisories in thenext16.4.0 dev dependency (GHSA-2464-fhr4-w9xw, GHSA-673q-mjm6-r5xr); bumped to 16.4.2.npm trusted publishing
The org-level
NPM_TOKENsecret is gone, so all npm publishes go through trusted publishing (OIDC). The release job already uses OIDC (environment: release,id-token: write, upgraded npm,NPM_CONFIG_PROVENANCE: true, no npm tokens). To matchlabd/commercetools-node-mock, this PR also:push-with-git-cli: truetochangesets/actionpackage.jsonrepository.urltogit+https://github.com/labd/nextjs-basic-auth-middleware.gitandpublishConfig.provenancetotrueOn npmjs.com,
nextjs-basic-auth-middlewareneeds a trusted publisher with repositorylabd/nextjs-basic-auth-middleware, workflowrelease.yamland environmentrelease.pnpm 12
Already on
pnpm@12.13.0; follow-up fixes:.npmrc(pnpm config get savePrefixreturnedundefined), sosave-prefix,auto-install-peersandstrict-peer-dependenciesmoved topnpm-workspace.yaml(savePrefix: "",autoInstallPeers: true,strictPeerDependencies: false) and.npmrcwas removed. Verified withpnpm config get.minimumReleaseAge: 10080kept as-is (already present),trustPolicy: no-downgradeunchanged.pnpm install --frozen-lockfilepasses.labd/gh-actions-typescript/pnpm-install→ v1.1.0, withcache: falsein the release job.