Metaplex smart contracts and SDK.

Name	Program	SDK
Token Vault
Token Metadata
Auction
Metaplex

Smart contract SDK ackages are versioned indepenently since a contract isn't necessarily coupled to other contracts.

We use the following (pre|post)(version|publish) npm scripts to manage related checks, tagging, commiting and pushing the version bump.

• preversion: ensures that the package builds and its tests pass
• postversion: adds and commits the version bump and adds a tag indicating package name and new version, i.e. @metaplex-foundation/[email protected]
• prepublish: ensures that the package builds and its tests pass again (just to be really sure)
• postpublish: pushes the committed change and new tag to github

In order to version and then publish a package just run the following commands from the folder of the package you want to update:

• npm version <patch|minor|major>
• npm publish

As you note if version + publish succeeds the scripts end up pushing those updates to the master branch. Therefore please ensure to be on an up to date master branch before running them. Please don't ever publish from another branch but only from the main one with only PR approved changes merged.

To report a security issue, please follow the guidance on the SECURITY page.