avo 3.2.11-alpha.0 → 3.2.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -49,4 +49,4 @@ For more documentation, visit [https://www.avo.app/docs/implementation/cli](http
|
|
|
49
49
|
1. Verify that the changes in the _Unreleased_ section in CHANGELOG.md are accurate, create a new heading with the correct semantic version then move the content from the _Unreleased_ section there
|
|
50
50
|
2. Update the semantic version in `package.json` to match the one you just created in the changelog
|
|
51
51
|
3. Commit with the message `Release <version>` and push the changes
|
|
52
|
-
4. Publish the package to npm (you'll need to be a maintainer of the avo project in npm): `npm publish`
|
|
52
|
+
4. Publish the package to npm (you'll need to be a maintainer of the avo project in npm): `npm publish`. To publish a pre-release, use `npm publish --tag next` (or `--tag beta`)
|
package/package.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "avo",
|
|
3
|
-
"version": "3.2.11
|
|
3
|
+
"version": "3.2.11",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "The command-line interface for Avo",
|
|
6
6
|
"author": "Avo (https://www.avo.app)",
|
|
7
7
|
"repository": {
|
|
8
8
|
"type": "git",
|
|
9
|
-
"url": "https://github.com/avohq/avo.git"
|
|
9
|
+
"url": "git+https://github.com/avohq/avo.git"
|
|
10
10
|
},
|
|
11
11
|
"license": "MIT",
|
|
12
12
|
"homepage": "https://github.com/avohq/avo",
|