[OPTIC-RELEASE-AUTOMATION] release/v3.0.0-next.18 #204
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.
Optic Release Automation
This draft PR is opened by Github action optic-release-automation-action.
A new draft GitHub release v3.0.0-next.18 has been created.
Release author: @tomasciccola
If you want to go ahead with the release, please merge this PR. When you merge:
The GitHub release will be published
The npm package with tag next will be published according to the publishing rules you have configured
The following tags will be updated to point to the latest appropriate commit: v3
If you close the PR
What's Changed
Role
data type by @gmaclennan in https://github.com/digidem/mapeo-schema/pull/127deleted
field to common (proto and schema) by @tomasciccola in https://github.com/digidem/mapeo-schema/pull/138refs
property from schemas by @EvanHahn in https://github.com/digidem/mapeo-schema/pull/196configMetadata
toprojectSettings
by @tomasciccola in https://github.com/digidem/mapeo-schema/pull/197New Contributors
Full Changelog: https://github.com/digidem/mapeo-schema/commits/v3.0.0-next.18