@sproutsocial/racine 7.4.0-beta-momo.1 → 7.4.0-beta-unc-momo.0

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Change Log
 
+## 7.3.5
+
+### Patch Changes
+
+- a929081: Fix quoting of package version in deprecate command in beta release action.
+
 ## 7.3.4
 
 ### Patch Changes

package/README.md

@@ -160,27 +160,33 @@ When making changes to Racine it often not possible to be certain that your chan
 
 #### **Releasing a beta**
 
-To release a beta version, commit your current changes and then run `yarn beta:release`. This command will create a new beta version with a semantic bump level based on your changeset(s), and include a differentiating identifier from your git user email name. For example, if [Bill Foehring](bfoehring@sproutsocial.com) was making a minor change to versions `6.55.3`, the command would: 
-1. create version `6.56.0-beta-bfoehring.0`,
+To release a beta version, commit your current changes and then run `yarn beta:release`. This command will create a new beta version with a semantic bump level based on your changeset(s), and will prompt you to include a differentiating suffix. Alternatively, you can specify the suffix as a param to the command. For example, if making a minor change to versions `6.55.3`, executing `yarn beta:release uncle-momo` would: 
+1. create version `6.56.0-beta-uncle-momo.0`,
 1. add a corresponding tag in git,
-1. and publish the new beta version to the npm registry.
+1. push the tag and version commit to Github,
+1. run the *beta-release* Github action,
+1. publish your new beta version to the npm registry.
 
-Once a beta release is published you can include it as a dependency from `web-app-core` or `seeds`.
+Once the action completes, your beta will be available in the *Current (distribution) Tags* on [NPM](https://www.npmjs.com/package/@sproutsocial/racine?activeTab=versions). Note: your published beta is marked as *deprecated* to prevent it from showing in the package's *Version History*
 
-The differentiating identifier is necessary to enable if two or more developers to concurrently create their own beta versions from the current version of Racine. Without the identifiers, the name of the beta versions could collide.
+Once you beta release is published, you can include it as a dependency from `web-app-core` or `seeds`.
+
+The differentiating suffix is necessary to enable if two or more developers to concurrently create their own beta versions from the current version of Racine. Without the suffixes, the names of the beta versions could collide.
+
+##### **Modify your beta**
+
+As you continue to make changes, rerunning `yarn beta:release` will release a new version of your beta. From the example above, it would create `6.56.0-beta-uncle-momo.1` as the next beta release. Running it again would create `6.56.0-beta-uncle-momo.2` and so on...
 
 #### **Checking beta status**
 
 Run `yarn beta:status` to see the info Racine has about your current beta version.
 
-As you continue to make changes, rerunning `yarn beta:release` will release a new version of your beta. From the example above, it would create `6.56.0-beta-bfoehring.1` as the next beta release. Running it again would create `6.56.0-beta-bfoehring.2` and so on...
-
-#### **Deprecating a beta**
+#### **Completing a beta**
 
-When you are satisfied that all of your changes are correct, you can end your beta by running `yarn beta:deprecate`. This will:
-- delete any beta metadata,
+When you are satisfied that all of your changes are correct, you can end your beta by running `yarn beta:complete`. This will:
+- remove any local and remote git tags for your beta,
 - restore the original version within `package.json`,
-- deprecate any beta releases on the registry for this version.
+- delete any beta metadata.
 
 Doing so will prime the changeset mechanism to complete the standard release process. (Note: The version of the final release is set at the last moment to ensure it actually is properly set the next valid semantic version as other versions of Racine may have been released during the time you are working on yours.)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sproutsocial/racine",
-  "version": "7.4.0-beta-momo.1",
+  "version": "7.4.0-beta-unc-momo.0",
   "license": "MIT",
   "files": [
     "__flow__",