Repository navigation
Publish releases only from owner-approved tags, add contribution and security policy - #5
Merged
Merged
Conversation
The repository is public but had no contribution guide, security policy or issue template, so reports could leak session content in public issues. These follow pi-claude-pro, adapted to an extension without account or live checks.
Every push to main ran the npm publication step. The merge of #3 tried to publish 0.2.0 and failed only because no trusted publisher exists yet. This ports the pi-claude-pro release lifecycle: CI validates version changes and lockfile metadata, merges only prepare a version, and publication needs an explicit v* tag on main, successful CI on that commit, and owner approval of the npm environment. An existing npm version must come from the same commit. CI also runs weekly and against the latest Pi packages.
HugoLopes45
changed the title
HugoLopes45
added a commit
that referenced
this pull request
Oct 6, 2026
The old README assumed knowledge of compaction, tokens and thresholds. This rewrite, in ASD-STE100 style: - explains the terms and the sequence of a session; - documents every `contextKit` setting with its allowed values, default and an example; - adds recipes, limits and questions. Checked against the code: - Defaults, validation rules and the warning text match `src/config.ts` and `extensions/index.ts`. - `soft` writes Pi's summary at the extension threshold (#4). Only `[]` waits for Pi's own limit. - The release section is unchanged from #5.
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
1 participant
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
release.ymlran on every push tomainand tried to publish to npm. Merging #3 started such a run; it failed only because no npm trusted publisher exists yet. The repository is public, but it had no security policy, so a report could leak session content in a public issue.What
This change:
scripts/release.tsand its tests:npm run check.vX.Y.Ztag onmain.release.yml: manual Publish release from a tag. Only the owner can start it. It needs successful CI on the exact commit and approval of thenpmenvironment.ci.yml: weekly run, manual run, version-change check, and a check against the latest Pi packages on Node 24.CONTRIBUTING.md,SECURITY.mdand the bug template.Repository settings already applied:
npmenvironment has the owner as required reviewer (self-review allowed) and accepts onlyv*tags.Immutable release tagsruleset blocks updates and deletion ofv*tags.Releaseworkflow is disabled until this PR is merged.Checks
npm run checkpasses: 128/128 tests.node scripts/release.ts check <main sha>printsversion=0.2.0,changed=false.gh workflow enable release.yml.release.yml, environmentnpm).pi-context-kitis not on npm yet.