Skip to content

feat(release)!: protect Ragmir with dual licensing - #148

Merged
jb-thery merged 1 commit into
mainfrom
release/v3.0.0
Jul 18, 2026
Merged

feat(release)!: protect Ragmir with dual licensing#148
jb-thery merged 1 commit into
mainfrom
release/v3.0.0

Conversation

@jb-thery

Copy link
Copy Markdown
Member

Release highlights

  • keep Ragmir open under AGPL-3.0-only and offer commercial terms for proprietary use
  • give teams one clear licensing path across npm, documentation, the website, and the wiki

Release details

  • Licensing: adopt AGPL-3.0-only from v3.0.0 while preserving earlier release terms
  • Commercial: document a separate signed agreement for proprietary and hosted use
  • Packages: ship LICENSE, COMMERCIAL-LICENSE.md, and NOTICE in all three npm packages
  • Guardrails: reject inconsistent manifests or incomplete release tarballs during validation
  • Landing and SEO: expose both paths in localized copy, footer links, and structured data
  • Contributions: require rights that keep the AGPL and commercial paths sustainable

Breaking change

Ragmir source releases from v3.0.0 use AGPL-3.0-only instead of MIT. Releases before v3.0.0
retain the license published with those versions.

Verification

  • pnpm validate
  • 20 landing tests and 499 Core tests
  • Astro checks and static production build
  • npm package metadata and tarball contents
  • publint, semantic-release smoke, release artifacts, and dependency audit
  • Linux x64 and macOS ARM64 portability checks, CodeQL, and Commitlint on develop
  • GitNexus change detection, low risk and no affected execution flows

Delivery after merge

  • semantic-release must predict and publish v3.0.0
  • verify all three npm packages, provenance, checksums, and the curated GitHub release
  • deploy the localized landing to staging and production with PUBLIC_RAGMIR_VERSION=3.0.0
  • publish the updated licensing page in the GitHub wiki

Release highlights:
- keep Ragmir open under AGPL-3.0-only and offer commercial terms for proprietary use
- give teams one clear licensing path across npm, documentation, the website, and the wiki

Release details:
- **Licensing:** adopt AGPL-3.0-only from v3.0.0 while preserving earlier release terms
- **Commercial:** document a separate signed agreement for proprietary and hosted use
- **Packages:** ship LICENSE, COMMERCIAL-LICENSE.md, and NOTICE in all three npm packages
- **Guardrails:** reject inconsistent manifests or incomplete release tarballs during validation
- **Landing and SEO:** expose both paths in localized copy, footer links, and structured data
- **Contributions:** require rights that keep the AGPL and commercial paths sustainable

Verification:
- pass pnpm validate, including 20 landing tests and 499 Core tests
- pass Linux x64 and macOS ARM64 portability checks, CodeQL, and Commitlint
- confirm AGPL metadata and canonical licensing files inside every generated npm tarball

BREAKING CHANGE: Ragmir source releases from v3.0.0 use AGPL-3.0-only instead of MIT.
@jb-thery
jb-thery merged commit 3bb31d4 into main Jul 18, 2026
15 checks passed
@jb-thery
jb-thery deleted the release/v3.0.0 branch July 18, 2026 19:51
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant