Repository navigation
Promote integration to main - #356
Merged
Merged
Conversation
Closes #133 Signed-off-by: Bar Kaduri <bar@capsule.security> Signed-off-by: rocklambros <rock@rockcyber.com>
rocklambros
requested review from
GangGreenTemperTatum,
Lrd0036,
afogel,
almogbhl,
artmaro,
bar-capsule,
mamicidal,
sclintonowasp and
stefanoamorelli
as code owners
October 29, 2026 14:13
github-project-automation
Bot
moved this from Needs triage
to Done
in ACS Project Tracker
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.
1 commit(s) ahead. Merging publishes the site and every schema $id URI. Merge with a merge commit, not a squash: squashing flattens the specification history that makes a schema change reviewable later.
What this ships
This is not a release.
version.txtstays 0.1.4, so no tag is created. No schema changes.docs/topics/faq.md, with its one-linemkdocs.ymlnav entry (PR Add FAQ to docs/topics #20, issue [Docs] No single page answers the questions four audiences keep asking #133).For implementers
Nothing changes on the wire. The FAQ is marked non-normative and points at the conformance chapter for requirement levels.
Roadmap
Merging delivers #133.