[OPTIC-RELEASE-AUTOMATION] release/v3.0.0-next.0

[optic-release-automation]

Optic Release Automation

This draft PR is opened by Github action optic-release-automation-action.

A new draft GitHub release v3.0.0-next.0 has been created.

Release author: @gmaclennan

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 latest 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

• The new draft release will be deleted and nothing will change

What's Changed

• build(deps): bump handlebars from 4.1.2 to 4.5.3 by @dependabot in https://github.com/digidem/mapeo-schema/pull/3
• feat: protocol buffers, json schema, & types for each by @tomasciccola in https://github.com/digidem/mapeo-schema/pull/22
• feat: versioned protobufs by @tomasciccola in https://github.com/digidem/mapeo-schema/pull/32
• feat: refactor type to schemaType by @tomasciccola in https://github.com/digidem/mapeo-schema/pull/41
• better exporting of types by @tomasciccola in https://github.com/digidem/mapeo-schema/pull/43
• Type exports by @tomasciccola in https://github.com/digidem/mapeo-schema/pull/47
• chore: add npm release action by @gmaclennan in https://github.com/digidem/mapeo-schema/pull/49
• chore: remove build-command from release action by @gmaclennan in https://github.com/digidem/mapeo-schema/pull/50
• Revert "chore: remove build-command from release action (chore: remove build-command from release action #50)" by @gmaclennan in https://github.com/digidem/mapeo-schema/pull/52

New Contributors

• @tomasciccola made their first contribution in https://github.com/digidem/mapeo-schema/pull/22
• @gmaclennan made their first contribution in https://github.com/digidem/mapeo-schema/pull/49

Full Changelog: https://github.com/digidem/mapeo-schema/commits/v3.0.0-next.0

[gmaclennan]

@tomasciccola merging this should run the release workflow and publish to npm under the next tag. I have also changed the package name from mapeo-schema to @mapeo/schema, so I don't think there is a risk of accidentally publishing a version that will affect previous Mapeo versions. Can you review https://github.com/digidem/mapeo-schema/blob/master/.github/workflows/release.yml and if so I can try merging this and see if the npm publish works

[gmaclennan]

Going ahead with merge to test the publish flow, since this should be minimal risk (npm package name is different so no danger of affecting the current mapeo-schema@2