Skip to content

[bundle] Update Spec Kit for Azure DevOps bundle to v0.4.0 - #5454

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
community/5428-update-ado-bundle-e4eec5b4c094c9b8
Draft

github-actions[bot] wants to merge 1 commit into
mainfrom
community/5428-update-ado-bundle-e4eec5b4c094c9b8

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Updates the existing ado community bundle entry in bundles/catalog.community.json from 0.3.2 to 0.4.0.

Catalog changes

  • Updated version to 0.4.0
  • Updated download_url to the tag-pinned release asset:
    • https://github.com/praveenlavu/spec-kit-ado/releases/download/v0.4.0/ado-0.4.0.zip
  • Updated sha256 to the digest computed from the downloaded archive:
    • aa77078fc2ed14775f9a759699f4a1a948d56a27b47b5739fc16dc810747ff27
  • Updated top-level updated_at to 2026-11-16T00:00:00Z

Documentation changes

  • Reviewed docs/community/bundles.md; the existing row for Spec Kit for Azure DevOps already matched the validated submission metadata (name, description, role, provides, required-catalog status, and repository), so no row text change was required.

Validation results

  • Issue title prefix check passed ([Bundle]:)
  • Bundle ID/version syntax checks passed (ado, 0.4.0)
  • Repository and documentation URLs are public GitHub URLs
  • Repository contains required files (bundle.yml, README.md, LICENSE)
  • bundle.yml metadata matches submission (id/name/version/role/author/license/spec-kit requirement/components)
  • Download URL passed repository/pinning/tag-semver checks and allowed-character validation
  • Download request returned HTTP 200
  • Release v0.4.0 exists and contains the exact ZIP asset ado-0.4.0.zip
  • Submitted checksum matched downloaded archive (sha256sum --check --strict: OK)
  • Proposed catalog entry JSON validated: single ado entry; required fields and values match; provides counts valid; tags valid; verified: false
  • Required catalogs/testing checklist/submission requirements/example usage checks passed

Closes #5428

cc @praveenlavu

Generated by 📦 Add Community Bundle from Issue Submission for #5428 · copilot · gpt53codex · 30.8 AIC · ⌖ 0.713 AIC · ⊞ 27.3K · ◷

Update the `ado` entry in `bundles/catalog.community.json` to version 0.4.0,
including the tag-pinned release asset URL and archive SHA-256 digest from the
validated download.

Documentation review: `docs/community/bundles.md` already matched the submitted
name, description, role, provided components, catalog requirement status, and
repository link, so no row content change was required.

Validation results:
- Issue title format check passed (`[Bundle]:` prefix present)
- Bundle ID/version format checks passed (`ado`, `0.4.0`)
- Repository and docs URL checks passed (public GitHub URLs)
- Required repository files present (`bundle.yml`, `README.md`, `LICENSE`)
- Manifest metadata matches submission and proposed catalog entry
- Release artifact URL pinning checks passed (same repo, tag-pinned, semver-aligned)
- Artifact download returned HTTP 200 and SHA-256 matched submitted checksum
- Release contains the exact ZIP asset (`ado-0.4.0.zip`)
- Proposed catalog JSON shape/content checks passed (`verified: false`, tags/provides/requires valid)
- Required component catalogs, testing checklist, and submission requirements checks passed

Closes #5428
cc @praveenlavu

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Assisted-by: GitHub Copilot (model: gpt-5.3-codex, autonomous)
@github-actions github-actions Bot added automated bundle-submission Community bundle catalog submission labels Nov 16, 2026
Copilot AI adaptive review requested due to automatic review settings November 16, 2026 20:53
@github-actions github-actions Bot mentioned this pull request Nov 16, 2026
13 tasks done

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔵 Needs a closer look

The catalog points bundle installs to an external v0.4.0 ZIP that cannot be independently fetched or rebuilt here, and the companion catalogs and published digest still require maintainer confirmation.

No open issues 🎉

What changed in this PR

Updates the Spec Kit for Azure DevOps community bundle catalog entry from version 0.3.2 to 0.4.0 with the validated release artifact and checksum.

Changes:

  • Bumps the ado bundle version to 0.4.0.
  • Updates the tag-pinned download URL and SHA-256 digest.
  • Refreshes the catalog timestamp while preserving existing metadata and documentation.
File Description
bundles/​catalog.community.json Updates the Azure DevOps community bundle release metadata, artifact URL, checksum, and catalog timestamp.

Review effort: Lite (adaptive)

@mnriem mnriem added the triage-must-have Verdict: high-value, important work for Spec Kit — do first label Nov 16, 2026
@mnriem
mnriem requested an adaptive review from Copilot November 16, 2026 23:56

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔵 Needs a closer look

The catalog now references an externally hosted release asset whose contents and checksum cannot be independently verified because the review environment cannot fetch it.

No open issues 🎉

Review effort: Lite (adaptive)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated bundle-submission Community bundle catalog submission triage-must-have Verdict: high-value, important work for Spec Kit — do first

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bundle]: Add ado (update to 0.4.0)

2 participants