Repository navigation
docs: record v0.1.0 release and add security and contributing guides - #15
Merged
Merged
Conversation
Record the successful v0.1.0 release in decision 0024, the readiness checklist and the plan, and note in decision 0025 that the owner will configure branch protection manually. Add SECURITY.md for private vulnerability reports and CONTRIBUTING.md with the repository's checks and commit conventions. Fix the README link to the action-header example, which moved to the actionheader package.
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.
Prepares the repository for going public: it records the v0.1.0 release and adds the two files outside contributors look for first.
Changes
docs/release-readiness.mdanddocs/plan.mdnow record that Release Please completed end to end and published v0.1.0 at 9423302. The plan's release item is ticked.SECURITY.md. Directs reports to GitHub private vulnerability reporting, asks for synthetic credentials only, defines scope, and states that only the latest v0 minor receives fixes. It makes no response-time commitments.CONTRIBUTING.md. Covers Apache-2.0 contribution terms (section 5, no CLA), issue-first for API and trust-boundary changes, the AGENTS.md check commands, the semantic line-break convention, and Conventional Commit titles, including!for breaking changes (squash merges use the PR title).actionheader/example_test.goin refactor: move action-header selection to the actionheader package #8.Validation
Documentation only. Every relative link in every Markdown file resolves, the edited files render, and
git diff --checkis clean.Owner follow-up
Private vulnerability reporting is not currently enabled; the API returns 404 while the repository is private. Enable it under Settings → Code security when making the repository public, or SECURITY.md's reporting link won't work.