Skip to content

Commit

Permalink
Bump version to v0.8.0-alpha.3
Browse files Browse the repository at this point in the history
* [skip testnet]
  • Loading branch information
FabijanC committed Jun 22, 2023
1 parent b3b853b commit b4ce4fc
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 5 deletions.
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@shardlabs/starknet-hardhat-plugin",
"version": "0.8.0-alpha.2",
"version": "0.8.0-alpha.3",
"description": "Plugin for using Starknet tools within Hardhat projects",
"main": "dist/src/index.js",
"files": [
Expand Down
6 changes: 4 additions & 2 deletions www/docs/dev.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,11 +162,13 @@ $ npm version <NEW_VERSION>

This will also update `package-lock.json`, create a new commit, and create a new git tag.

You may want your version-bumping commit to contain the `[skip testnet]` string (documented [here](#testing-network)) to avoid testing on alpha-goerli (may postpone the version release significantly, if it will ever pass at all).

If for whatever reason the publishing workflow in CI/CD cannot be executed, the version can be released manually via `scripts/npm-publish.sh`, just be sure to have an NPM access token and that you have the rights to publish.

Apart from [npm](https://www.npmjs.com/package/@shardlabs/starknet-hardhat-plugin?activeTab=versions), releases are also tracked on [GitHub](https://github.com/0xSpaceShard/starknet-hardhat-plugin/releases) with [git tags](https://github.com/0xSpaceShard/starknet-hardhat-plugin/tags). Notice the prepended `v` in tag names.

When the tag is pushed:
After the npm package is released and the tag is pushed:

```bash
$ git push origin <TAG_NAME>
Expand All @@ -178,7 +180,7 @@ Users should be notified about the usage related changes. This can be done on Te

### Docs

New documentation is **automatically** deployed after publishing a new version with `scripts/npm-publish.sh`.
New documentation is **automatically** deployed after publishing a new version with `scripts/npm-publish.sh` (also part of CI/CD).

To manually deploy new documentation, run:

Expand Down

0 comments on commit b4ce4fc

Please sign in to comment.