chore: release 8.3.0 - #219
Merged
Merged
Conversation
…10506) (#183) Co-authored-by: Copilot <copilot@github.com> Co-authored-by: RonitKissis <ronitkisis1997@gmail.com>
Release-As: 8.0.0-alpha.0
Co-authored-by: Copilot <copilot@github.com> Co-authored-by: razbroc <77406876+razbroc@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
# Conflicts: # .release-please-manifest.json # CHANGELOG.md # package-lock.json # package.json # src/constants/core/constants.ts
…8284) (#208) Co-authored-by: razbroc <77406876+razbroc@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Graduate the 8.3.0 alpha line to a stable release. Release-As: 8.3.0
vitaligi
approved these changes
Aug 3, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Graduates the
8.3.0alpha line to a stable release. This brings everything currently onalphaintomasterand releases it as v8.3.0 — the same content as8.3.0-alpha.2, without the prerelease suffix.Does not include the pending work in #218, which is still open against
alpha.Contents
masteris an ancestor ofalpha, so this is a fast-forward of the 30 commits that accumulated across the8.3.0-alpha.0→8.3.0-alpha.2cycle. Headline items:subPathonfsStorageSchemakeywordson the base raster layer metadata schema (MAPCO-8284)SourceTyperefactorproductIdpattern fixHow the version is set
This PR adds one empty commit carrying a
Release-As: 8.3.0footer. On merge tomaster, release-please runs in stable mode (release-please-config.json) and opens a release PR that sets8.3.0inpackage.json,.release-please-manifest.jsonandCHANGELOG.md. Merging that release PR tagsv8.3.0, which triggerspublish.yamlto publish to npm underlatest.Side effect: repairs drifted release state
masteris currently inconsistent —.release-please-manifest.jsonsays8.1.0whilepackage.jsonsays8.2.0and tagv8.2.0exists, because8.2.0was bumped manually (#209) without updating the manifest or CHANGELOG. The release PR this produces will bring all three back into agreement at8.3.0.Note
alphaitself is deliberately untouched — theRelease-Asmarker lives on this branch, since pushing it toalphawould have triggered the prerelease workflow.