Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: scijava/scijava-scripts
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 8b1eabf
Choose a base ref
...
head repository: scijava/scijava-scripts
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 63ed3e4
Choose a head ref
  • 3 commits
  • 1 file changed
  • 1 contributor

Commits on Nov 6, 2025

  1. WIP: Support releasing within a multi-module repo 

    THIS IS NOT YET FUNCTIONAL. It is a first-cut AI-supported
modification to release-version.sh that implements an approach we think
is ultimately going to work, but still needs refinement and testing.

Bugs:
- the version prompt logic happens before the multi-module detection
- reverting the snapshot-to-release prep commit is insufficient:
  we also need to bump the released component version snapshot
  to next dev version everywhere it is a dependency in other modules

The workflow is to release only one module per invocation.

The steps are:
1. comment out all modules other than the one being released
2. roll back the target module's SNAPSHOT deps to newest release versions
3. run mvn release:prepare with the -pl flag pointing at target module
   - this excludes the aggregator itself from the reactor, to
     avoid future useless scijava-aggregator POMs on Central
4. squash the release + prep + bump commits into one on the main branch
5. continue business as usual: push main, rewrite release tag and push

The ci-build.sh probably still needs modification to use -pl as well.

Open questions:
- is -pl with release:prepare really needed? or only at perform step?
- do we squash the release prep commits into a single release commit?
  - or do we leave them as a sequence on the orphaned tag?
    @ctrueden
    ctrueden committed Nov 6, 2025
    Configuration menu
    Copy the full SHA
    ee5c43a View commit details
    Browse the repository at this point in the history

  2. TEMP: First attempt at fixing the two big bugs 

    - detect version of to-be-released component
- bump deps of that component to next snapshot
    @ctrueden
    ctrueden committed Nov 6, 2025
    Configuration menu
    Copy the full SHA
    933ada8 View commit details
    Browse the repository at this point in the history

  3. TEMP: include needed -pl flag in release.properties

    @ctrueden
    ctrueden committed Nov 6, 2025
    Configuration menu
    Copy the full SHA
    63ed3e4 View commit details
    Browse the repository at this point in the history
Loading