Skip to content

tools/upgrade-version updates the Change Date in LICENSE.txt #2895

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 30, 2025

Conversation

bfops
Copy link
Collaborator

@bfops bfops commented Jun 24, 2025

Description of Changes

We have sometimes missed this field when doing upgrades. This PR automates it as part of the rest of tools/upgrade-version.

Closes #2284.

API and ABI breaking changes

No runtime changes

Expected complexity level and risk

2

Testing

$ ( cd tools/upgrade-version && cargo run -- 1.2.3 ) 2>/dev/null && git diff LICENSE.txt
diff --git a/LICENSE.txt b/LICENSE.txt
index ca1f88fef..adca0d5e3 100644
--- a/LICENSE.txt
+++ b/LICENSE.txt
@@ -5,7 +5,7 @@ Business Source License 1.1
 Parameters
 
 Licensor:             Clockwork Laboratories, Inc.
-Licensed Work:        SpacetimeDB 1.2.0
+Licensed Work:        SpacetimeDB 1.2.3
                       The Licensed Work is
                       (c) 2023 Clockwork Laboratories, Inc.
                       
@@ -21,7 +21,7 @@ Additional Use Grant: You may make use of the Licensed Work provided your
                       Licensed Work by creating tables whose schemas are
                       controlled by such third parties.
 
-Change Date:          2030-06-04
+Change Date:          2030-06-24
 
 Change License:       GNU Affero General Public License v3.0 with a linking
                       exception

@bfops bfops requested a review from jdetter June 24, 2025 19:45
@bfops bfops added release-any To be landed in any release window no runtime change This change does not affect the final binaries labels Jun 24, 2025
@bfops
Copy link
Collaborator Author

bfops commented Jun 24, 2025

SDK Tests failing spuriously. I will re-run once the other workflows finish.

Copy link
Collaborator

@jdetter jdetter left a comment

Choose a reason for hiding this comment

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

I confirmed with TL that this behavior is correct. Thanks @bfops !

@bfops bfops added this pull request to the merge queue Jun 30, 2025
Merged via the queue into master with commit 29a0df4 Jun 30, 2025
29 of 30 checks passed
@bfops bfops deleted the bfops/upgrade-version-license branch June 30, 2025 17:33
joshua-spacetime pushed a commit that referenced this pull request Jul 1, 2025
Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no runtime change This change does not affect the final binaries release-any To be landed in any release window
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tools/upgrade-version should update LICENSE.txt properly
2 participants