Skip to content

Release 1.3.1 - #101

Merged
wf9a5m75 merged 1 commit into
mainfrom
release/1.3.1
Aug 16, 2026
Merged

Release 1.3.1#101
wf9a5m75 merged 1 commit into
mainfrom
release/1.3.1

Conversation

@wf9a5m75

Copy link
Copy Markdown
Contributor
  • Give BOM-managed Compose artifacts an explicit version so the published POM carries one. Maven Central rejects versionless dependencies, and consumers who do not import the Compose BOM cannot resolve them either.
  • Fix the BOM module list: it pointed at a nonexistent geojson-layer coordinate and omitted seven modules, compose among them.
  • Bump every submodule to its 1.3.1 release commit.
  • Repair the standalone builds and add a per-PR build check to each module.

All 17 module coordinates were verified to resolve on Maven Central before the BOM was regenerated.

- Give BOM-managed Compose artifacts an explicit version so the published POM
carries one (Maven Central rejects versionless dependencies, and consumers who
do not import the Compose BOM cannot resolve them)
- Fix the BOM module list: it pointed at a nonexistent geojson-layer coordinate
and omitted seven modules, compose among them
- Bump every submodule to its 1.3.1 release commit
- Repair the standalone builds and add a per-PR build check to each module
@wf9a5m75
wf9a5m75 merged commit 6752e29 into mainAug 16, 2026
@wf9a5m75
wf9a5m75 deleted the release/1.3.1 branch August 16, 2026 16:51
Sign up for freeto 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.

1 participant

@wf9a5m75