Skip to content

Release 0.3.0 - #35

Merged
wf9a5m75 merged 2 commits into
developfrom
chore/release-0.3.0
Oct 29, 2026
Merged

wf9a5m75 merged 2 commits into
developfrom
chore/release-0.3.0

Conversation

@wf9a5m75

Copy link
Copy Markdown
Contributor

Every published package except the react-icons family moves to 0.3.0.

  • Versions: js-sdk-core, js-sdk-react, js-vectorstyle, all 15 react-for-* providers, react-geojson, react-heatmap, react-kml, react-marker-clustering and react-vectortile, plus the root.
  • Internal ranges: every @mapconductor/* range on those packages moves to ^0.3.0. That includes the private reactnative-* packages, the templates and react-icons, so the workspace resolves a single copy of each package.
  • Release exclusion: npm-publish.yml gains an exclude input that leaves the named packages out of the preview, the publish and the visibility check. preflight-publish.mjs skips them too.
    • This release runs with exclude set to react-icons, react-icons-jp, react-icons-us and react-icons-weather.
    • react-icons stays 0.2.0, which is already on npm, but preflight would still check its range on js-sdk-core.
  • Submodules: each one gets a PR to develop. They point at those branches for now and move to develop once the PRs merge.
  • Lockfile: package-lock.json is regenerated.

Checked locally:

  • npm install, npm run build:packages, npm test and node scripts/api-surface.mjs check pass.
  • Preflight with the exclusion passes for 22 of 23 packages. The one failure is js-sdk-react, and the cause is local only: npm pack crashes on the 4.2GB of ignored Android build output there, which a clean checkout doesn't have.

- every published package except the react-icons family moves to 0.3.0, and
  every @MapConductor range on them to ^0.3.0 (the private reactnative-* and
  templates included, so the workspace resolves one copy of each)
- npm-publish.yml: an `exclude` input, for packages left out of a release;
  preflight-publish.mjs leaves them out too
- the submodules point at their 0.3.0 branches; they move to develop once
  those merge
- package-lock.json regenerated
@wf9a5m75
wf9a5m75 merged commit 51f5a7e into develop Oct 29, 2026
3 checks passed
@wf9a5m75
wf9a5m75 deleted the chore/release-0.3.0 branch October 29, 2026 06:44
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.

1 participant