Skip to content

Releases run only package security checks; fix npm publish; GitHub Pages - #39

Merged
MelbourneDeveloper merged 1 commit into
mainfrom
release-no-gates
Oct 31, 2026
Merged

MelbourneDeveloper merged 1 commit into
mainfrom
release-no-gates

Conversation

@MelbourneDeveloper

Copy link
Copy Markdown
Collaborator

TLDR

Releases publish straight away with only the package security checks, npm publish works, and the website deploys to GitHub Pages.

Details

  • release.yml: drops the CodeQL gate and make ci (main only takes squash-merged PRs that passed CI). Keeps cargo deny, npm audit and cargo package. Drops .NET, strace, coverage and test tooling. Timeout 45 → 30 min.
  • codeql.yml: removes the now-unused workflow_call gate input and its enforce step; PR and weekly scans are unchanged.
  • scripts/npm-publish-or-skip.sh: publishes the tarball by absolute path. npm read dist/x.tgz as GitHub repo dist/x.tgz, which failed the v0.1.0 npm publish.
  • pages.yml (new): builds the Eleventy site with the Pages base path and deploys it on v* tags and workflow_dispatch. Pages source is already set to GitHub Actions.

Tests

  • zizmor offline: no new findings (3 low on main → 2 low).
  • Site built locally with --pathprefix=/lspkit/; every link resolves under /lspkit/.

Spec/doc changes

[REL-GATES] and the [REL-REGIME] table in docs/specs/lspkit-spec.md, plus docs/plans/publishing-plan.md.

Breaking changes

None.

Supersedes #38.

🤖 Generated with Claude Code

@MelbourneDeveloper
MelbourneDeveloper merged commit cbb5dfb into main Oct 31, 2026
10 checks passed
@MelbourneDeveloper
MelbourneDeveloper deleted the release-no-gates branch October 31, 2026 06:01
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