Skip to content

build: keep dependency locking, drop nebula.release (into #68) - #72

Merged
soloturn merged 1 commit into
MovingBlocks:feat/nebula-versioning-and-lockfilefrom
SiliconSaga:build/locking-without-nebula
Sep 28, 2026
Merged

soloturn merged 1 commit into
MovingBlocks:feat/nebula-versioning-and-lockfilefrom
SiliconSaga:build/locking-without-nebula

Conversation

@agent-refr

Copy link
Copy Markdown

AI-assisted change proposal. Filed by agent driven by @Cervator via GDD.

Summary

Targets #68's branch, not master: it keeps the dependency locking half of #68 and removes the nebula.release half, so #68 can land as a locking-only change.

  • Terasology (engine/module.txt), gestalt (gradle.properties) and CrashReporter (gradle.properties) all carry a hand-edited -SNAPSHOT version that Jenkins publishes from the long-lived branches. That is the community's one release convention today, and adopting tag-driven versioning in a small utility first would leave it the odd repo out.
  • With nebula active, the existing Jenkinsfile's plain publish on master resolves to 5.2.0-dev.9+c305ae6 (checked with :cr-core:properties on this branch), so the 5.2.0-SNAPSHOT stream Artifactory holds today would stop updating and a new dev version would land per merge.
  • If the community moves to tag-driven releases later, that wants a written process across repos first; this repo would then be a fine second adopter.

Dependency locking is unaffected and stays exactly as #68 wrote it, including -PnoLock.

Test plan

Related

Terasology, gestalt and this repo all version from a hand-edited SNAPSHOT string that Jenkins publishes from long-lived branches. nebula.release would make CrashReporter the one Maven-published repo versioned from git tags, and a plain `publish` on master would ship `5.2.0-dev.N+sha` in place of today's `5.2.0-SNAPSHOT`. Locking stands on its own.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: c214e4da-0bce-4947-ae9e-6bc31731d8ee

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

Comment @coderabbitai help to get the list of available commands.

@agent-refr
agent-refr changed the base branch from master to feat/nebula-versioning-and-lockfile September 28, 2026 15:22
@soloturn
soloturn merged commit 84ef6e5 into MovingBlocks:feat/nebula-versioning-and-lockfile Sep 28, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants