Relicense azphalt from MIT to Apache-2.0

[HereLiesAz]

Summary

Relicenses azphalt from MIT to Apache-2.0, as requested. Apache-2.0 keeps every freedom MIT gave and adds an explicit patent grant plus patent retaliation. For a standard that other hosts implement, that grant is the point.

• Licence files: LICENSE is now the canonical Apache License 2.0 text, taken from apache.org. A new NOTICE holds the copyright line and says that extensions keep their own licences.
• Package metadata: every workspace package's "license" field is now Apache-2.0. The exception is the create-azphalt templates: their field is the default for a creator's own project, and the scaffolder still asks which licence they want.
• Changeset: .changeset/apache-2.md gives a minor bump to each published package.
• Prose: updated where the standard's own licence is named:
  • README (licence section and layout);
  • the store's terms, § 1;
  • spec/extension-manifest.md and spec/marketplace-integrity.md, mirrored into docs/specs;
  • the create-azphalt readme;
  • docs/RATIONALE.md § Licensing, which now argues for Apache-2.0 over MIT and EPL.
• Left alone: the Next.js storefront's copies. The PR that retires Next.js deletes them.

Also fixed: .changeset/publish-endpoint.md (from #223) mixed private apps with the published @azphalt/azdk. Changesets v3 refuses that as a "mixed changeset", so it would have failed the next release. I split it into two files, and changeset status now passes.

Validation

• pnpm install --frozen-lockfile passes; the lockfile is unchanged.
• The docs build passes with no dead links.
• changeset status passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QwYWVPse8spRrfMMcuTJPv

---

Generated by Claude Code

Summary by Sourcery

Adopt Apache License 2.0 across the azphalt standard and its published packages while preserving independent extension licensing.

Bug Fixes:

• Separate the Repository API publish-endpoint changeset from the azdk changeset so Changesets can process the release metadata successfully.

Enhancements:

• Relicense the azphalt standard, source packages, applications, examples, and documentation from MIT to Apache License 2.0, including the associated patent protections.
• Document that extensions retain their own licences while preserving creator-selected licensing in create-azphalt templates.

Documentation:

• Update README, specifications, marketplace terms, rationale, and scaffolding documentation to reflect Apache-2.0 licensing.

Chores:

• Add Apache-2.0 NOTICE information and minor release changesets for the affected published packages.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
azphalt	Building	Preview	Sep 27, 2026 6:02am UTC

[sourcery-ai]

Reviewer's Guide

Relicenses azphalt’s repository and published packages from MIT to Apache-2.0, adds the required NOTICE and documentation/metadata updates, preserves creator-selected extension licenses, and splits a mixed Changesets entry so release validation passes.

Flow diagram for Apache-2.0 licensing metadata and release validation

flowchart TD
    Relicense["Relicense repository and packages\nMIT → Apache-2.0"] --> Files["Update LICENSE and add NOTICE"]
    Files --> Metadata["Update package license fields"]
    Metadata --> Docs["Update README, specs, terms, and rationale"]
    Docs --> Changesets["Add Apache-2 changeset\nminor bumps for published packages"]
    Changesets --> Split["Separate repository publish changeset\nfrom private storefront apps"]
    Split --> Status["changeset status passes"]

Loading

File-Level Changes

Change	Details	Files
Relicense the repository and published packages from MIT to Apache-2.0 while preserving creator-selected licensing for generated projects and extension content.	Replace the canonical license text and add copyright/extension-license guidance in NOTICE. Update package metadata across applications, packages, examples, and docs; keep scaffolder output driven by the creator’s license choice. Revise README, terms, rationale, and duplicated specifications to describe Apache-2.0 and distinguish repository code from extensions. Add a minor changeset covering published packages and create-azphalt.	LICENSE NOTICE README.md apps/repository-server/package.json apps/storefront-cmp/package.json apps/storefront/package.json apps/storefront-react/public/terms.html docs/RATIONALE.md docs/package.json docs/specs/extension-manifest.md docs/specs/marketplace-integrity.md examples/gallery/package.json examples/invert/package.json packages/*/package.json packages/create-azphalt/readme.md spec/extension-manifest.md spec/marketplace-integrity.md .changeset/apache-2.md
Repair the existing publish-endpoint changeset so Changesets accepts the application and published-package releases independently.	Move repository-server and storefront package bumps and their publish-endpoint description into a separate changeset. Leave @azphalt/azdk’s error-code changes in the original changeset. Ensure the resulting changesets no longer mix private applications with the published SDK.	.changeset/publish-endpoint.md .changeset/publish-endpoint-apps.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Sorry @HereLiesAz, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 17 hours by commenting @sourcery-ai review. Upgrade to get a review now.