Skip to content

[docs] Update documentation for features from 2026-05-18#1380

Closed
danielmeppiel wants to merge 1 commit into
mainfrom
docs/daily-update-2026-05-19-68e00e84fa1c1a60
Closed

[docs] Update documentation for features from 2026-05-18#1380
danielmeppiel wants to merge 1 commit into
mainfrom
docs/daily-update-2026-05-19-68e00e84fa1c1a60

Conversation

@danielmeppiel
Copy link
Copy Markdown
Collaborator

Documentation Updates - 2026-05-18

This PR updates the documentation based on features merged in the last 24 hours.

Features Documented

Changes Made

  • Updated docs/src/content/docs/reference/cli/pack.md:

    • Added --check-versions flag: validates per-package versions against marketplace.versioning.strategy
    • Added --check-clean flag: regenerates marketplace.json into a temp dir and diffs against the committed copy
    • Updated --json envelope description to mention new version_alignment and drift keys
    • Added exit codes 3 (version misalignment) and 4 (marketplace.json drift)
    • Added "Release gates (CI)" examples section with usage and marketplace.versioning config snippet
  • Updated docs/src/content/docs/reference/manifest-schema.md:

    • Added versioning row to the marketplace: block fields table (Section 7.2)
    • Added new Section 7.7: marketplace.versioning -- covers lockstep, tag_pattern, and per_package strategies with a full YAML example

Merged PRs Referenced

Notes

The following merged PRs were reviewed but required no documentation changes (either already documented by the PR author or internal/infrastructure changes):

Generated by Daily Documentation Updater · ● 1.4M ·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/daily-doc-updater.md@b87234850bf9664d198f28a02df0f937d0447295
  • expires on May 21, 2026, 6:13 AM UTC

…versioning schema

- Add --check-versions and --check-clean flags to apm pack reference
- Add exit codes 3 and 4 for the new release gates
- Update --json envelope description to include new version_alignment and drift keys
- Add release gates CI examples and versioning strategy config snippet
- Add marketplace.versioning section (7.7) to manifest-schema.md
  covering lockstep / tag_pattern / per_package strategies

Triggered by #1365 (feat(pack): add --check-versions and --check-clean release gates)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 19, 2026 06:13
@danielmeppiel danielmeppiel added automation Deprecated: use type/automation. Kept for issue history; will be removed in milestone 0.10.0. documentation Deprecated: use type/docs. Kept for issue history; will be removed in milestone 0.10.0. labels May 19, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the reference documentation to cover newly added apm pack release-gate flags and the marketplace.versioning manifest schema block introduced in recent feature work (notably #1365).

Changes:

  • Documented apm pack --check-versions / --check-clean, their JSON envelope keys, and exit codes.
  • Extended the manifest schema reference to include marketplace.versioning and described available strategies.
  • Added a CI-oriented “Release gates” usage section to the apm pack reference page.
Show a summary per file
File Description
docs/src/content/docs/reference/cli/pack.md Adds flag docs for release gates, JSON envelope notes, examples, and exit codes.
docs/src/content/docs/reference/manifest-schema.md Documents the new marketplace.versioning schema entry and adds a dedicated section describing it.

Copilot's findings

Comments suppressed due to low confidence (4)

docs/src/content/docs/reference/cli/pack.md:42

  • --check-clean is described as regenerating into a temp directory and diffing against the committed copy, and as "never" writing to the working tree. In the current implementation, the drift gate compares regenerated JSON to the on-disk artifact, and apm pack will still write outputs unless --dry-run is used. Please adjust wording to match the behavior (and clarify that --dry-run is required if you want a pure "check" run).
| `--check-clean` | off | Regenerate `marketplace.json` into a temp directory and diff it against the committed copy. Exits `4` when any format has drifted. Never writes to the working tree. Composes with `--dry-run` and `--json`. |

docs/src/content/docs/reference/cli/pack.md:107

  • In the CI examples, apm pack --check-clean (and the combined --check-versions --check-clean --json) should likely also use --dry-run; otherwise apm pack may rewrite marketplace artifacts before the drift check runs, which undermines the purpose of detecting drift and can dirty the workspace.
# Confirm committed marketplace.json is not stale (exits 4 on drift):
apm pack --check-clean

# Run both gates together; structured output for CI step summary:
apm pack --check-versions --check-clean --json

docs/src/content/docs/reference/cli/pack.md:118

  • The strategy summary is not aligned with the --check-versions implementation: tag_pattern checks for rendered tag collisions (it doesn't "check versions against build.tagPattern"), and per_package still fails if a local package is missing/invalid version (it only relaxes cross-package equality). Please update this sentence to reflect the actual gate semantics.
Strategies: `lockstep` (default) -- all package versions match the top-level `version`; `tag_pattern` -- versions are checked against the `build.tagPattern`; `per_package` -- no cross-package version constraint (gate never fails).

docs/src/content/docs/reference/manifest-schema.md:678

  • The strategy descriptions here don't match the implemented --check-versions behavior. tag_pattern uses build.tagPattern to render tags and fails on duplicate rendered tags across local packages; per_package relaxes cross-package equality but still fails when a local package has no/invalid version (or missing apm.yml). Please update these rows so users understand what is actually enforced.
| `lockstep` | All packages listed under `marketplace.packages` MUST share the same `version` value as the top-level `version` field. The most common convention for monorepo marketplaces. |
| `tag_pattern` | Versions are derived from the `build.tagPattern` template; cross-package version equality is not enforced. Suitable for semantic-release workflows where each package tags independently. |
| `per_package` | No cross-package version constraint. The `--check-versions` gate always passes; the field documents intent without enforcement. |
  • Files reviewed: 2/2 changed files
  • Comments generated: 2

| `-m`, `--marketplace FORMATS` | all configured | Comma-separated list of marketplace formats to build. Sentinels: `all` (every configured format), `none` (skip marketplace entirely). |
| `--marketplace-path FORMAT=PATH` | manifest default | Override the output path for a specific format. Repeatable. Example: `--marketplace-path codex=./dist/codex.json`. |
| `--json` | off | Emit machine-readable JSON to stdout. All logs move to stderr. Shape: `{ok, dry_run, warnings, errors, marketplace: {outputs: [...]}}`. |
| `--json` | off | Emit machine-readable JSON to stdout. All logs move to stderr. Shape: `{ok, dry_run, warnings, errors, marketplace: {outputs: [...]}, version_alignment, drift}`. The `version_alignment` and `drift` keys are always present; they are `null` when the corresponding gate flag was not passed. |
Comment on lines +666 to +669
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `strategy` | `enum` | REQUIRED | `lockstep` | One of `lockstep`, `tag_pattern`, or `per_package`. |

@github-actions
Copy link
Copy Markdown

This pull request was automatically closed because it expired on 2026-05-21T06:13:48.972Z.

Closed by Workflow

@github-actions github-actions Bot closed this May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation Deprecated: use type/automation. Kept for issue history; will be removed in milestone 0.10.0. documentation Deprecated: use type/docs. Kept for issue history; will be removed in milestone 0.10.0.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants