Migrate license to FSL-1.1-ALv2

[filipelautert]

Summary

• Replace license file with FSL-1.1-ALv2 (Functional Source License, Version 1.1, ALv2 Future License)
• Update build metadata (pom.xml / package.json) where applicable
• Update README.md license references where applicable

This aligns with the license migration completed in the main liquibase/liquibase repository in September 2025.

Reference

• FSL-1.1-ALv2 License Text
• Main repo license change

[coderabbitai]

📝 Walkthrough

Walkthrough

The repository licensing model is changed from Apache License 2.0 to Functional Source License 1.1 (ALv2 Future License). The original Apache 2.0 license file is removed, replaced with the FSL 1.1 license terms, and README documentation is updated to reflect the new licensing designation for Liquibase 4.

Changes

Cohort / File(s)	Summary
License Files LICENSE, LICENSE.txt	Replaced Apache License 2.0 with Functional Source License 1.1 (ALv2 Future License), which includes a grant of future Apache 2.0 license after a second anniversary.
Documentation README.md	Updated all Liquibase 4 licensing references from Apache 2.0 to FSL-1.1-ALv2 across version matrix, license notes, and tag guidance sections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately summarizes the main change—migrating the repository license from Apache 2.0 to FSL-1.1-ALv2.
Description check	✅ Passed	The description is directly related to the changeset, outlining the license migration objectives, affected files, and providing relevant references.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch migrate-to-fsl-license

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude finished @filipelautert's task in 44s —— View job

---

Review Complete

• Gather context
• Review changed files
• Post review feedback

---

One factual error found in README.md:

The PR changes this line:

- Automatically transitions to the Apache 2.0 license after two years

to:

- Automatically transitions to the FSL-1.1-ALv2 license after two years

This is incorrect. The FSL-1.1-ALv2 license text (in LICENSE.txt) explicitly states the future license grant is Apache License, Version 2.0 — not FSL-1.1-ALv2. The original wording ("transitions to the Apache 2.0 license after two years") was accurate and should be retained. Fix this →

All other changes look correct — the LICENSE file swap, README table and section updates for Liquibase 4's license, and the new LICENSE.txt content match the canonical FSL-1.1-ALv2 text.

[claude]

Claude finished @filipelautert's task in 1m 48s —— View job

---

Review Complete

• Gather context
• Review changed files
• Post review feedback

---

The previously flagged error ("Automatically transitions to the FSL-1.1-ALv2 license after two years") has been correctly fixed — line 208 of README.md now properly reads "Apache 2.0 license after two years" as the FSL-1.1-ALv2 text specifies.

One remaining concern in README.md: Multiple places now describe Liquibase 4.x as using "FSL-1.1-ALv2" (version table, upgrade guide, license section, and tag recommendations), but Liquibase 4 predates the FSL migration (September 2025) and was released under Apache 2.0. If the main liquibase/liquibase repo did not retroactively relicense 4.x code, these descriptions are inaccurate and could mislead users about the license that governs code they already received. Please confirm whether 4.x versions were explicitly relicensed as part of the September 2025 migration before merging.

All other changes look correct — the LICENSE → LICENSE.txt swap with canonical FSL-1.1-ALv2 text, copyright notice (© 2025 Liquibase Inc.), and the Apache 2.0 future-grant clause all look accurate.

[claude]

Claude finished @filipelautert's task in 1m 30s —— View job

---

Review Complete

• Gather context
• Review changed files
• Post review feedback

One inconsistency found:

The previous issue (incorrect "transitions to FSL-1.1-ALv2" instead of "Apache 2.0") was correctly fixed. However, the latest commit (bedc4c1) introduced a new contradiction: README.md line 121 now says "Apache v2" while all other Liquibase 4 references in the document (table, section heading, section body, tag descriptions) consistently say "FSL-1.1-ALv2". See the inline comment for the suggested fix.

LICENSE.txt content looks correct and matches the canonical FSL-1.1-ALv2 text.

[claude]

This line still says "Apache v2" but the rest of the document (table, section heading at line 213, section body at line 215, tag descriptions) all say "FSL-1.1-ALv2" for Liquibase 4 — this is an internal inconsistency introduced by the latest commit.

Suggested change

	- **Liquibase 4**: Uses Apache v2 license (always available)
	- **Liquibase 4**: Uses FSL-1.1-ALv2 license (always available)

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 121: Update the conflicting Liquibase 4 license statement so the README
is consistent: choose the correct license identifier (either "FSL-1.1-ALv2" or
"Apache v2") and apply it uniformly where Liquibase 4 is referenced (replace the
text at the current bullet that reads "**Liquibase 4**: Uses Apache v2 license
(always available)" to match the other occurrences or vice versa), and run a
quick search in the README for all occurrences of "Liquibase 4", "FSL-1.1-ALv2",
and "Apache v2" to ensure every mention (including the instances referenced
around lines 19, 213/215/387/400) uses the chosen, identical license phrase.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 700e8c4d-5d2c-4a0a-b9d2-416f365dea5d

📥 Commits

Reviewing files that changed from the base of the PR and between 946c4d1 and bedc4c1.

📒 Files selected for processing (3)

• LICENSE
• LICENSE.txt
• README.md

💤 Files with no reviewable changes (1)

• LICENSE

[claude]

Claude finished @filipelautert's task in 1m 4s —— View job

---

Review Complete

• Gather context
• Review changed files
• Post review feedback

---

LGTM — the previous issues have been fully resolved.

• README.md was rolled back (9b31bc7) and is now identical to main — no more inconsistencies.
• LICENSE.txt contains the correct canonical FSL-1.1-ALv2 text, with copyright © 2025 Liquibase Inc. and the future Apache 2.0 grant clause.
• The old Apache 2.0 LICENSE file has been removed.

No significant issues found.