chore: release#973
Conversation
6a24c95 to
23b151e
Compare
|
Hi @rakita , When will this release be finished? |
I have a few pending things to do, but it should be in the next few weeks. |
dc90666 to
e64e056
Compare
|
Hell yeah, I love to see it. |
34be95e to
2abc1cb
Compare
7697704 to
143b828
Compare
Signed-off-by: GitHub Action <action@github.com>
143b828 to
5b60fcb
Compare
|
@rakita is there a reason this was closed? |
don't know |
|
Reopen |
|
Would be nice to have it merged in and all the right semantic versioning. |
Totaly agree, i intended to merge PR and manually publish crates. It does not allow me to open it again it said branch is force-pushed or recreated |
|
Maybe it is some forbidden character. It failed with |
|
the commit where it started failing: #1028 |
|
Oh this is interesting. I'll take a closer look when i get a moment here and see if i can investigate. |
|
i think it is because if you didn't configure the github token for automatic crates publishing then the env part in the yaml should be removed: # if you configure the cargo registry token, the action will also publish the new version to crates.io
- name: Run release-plz
uses: MarcoIeni/release-plz-action@v0.5
with:
command: release-pr
env:
# The admin of the repository with need to configure the following secrets:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
Maybe it was just character count there is a limit of 64k characters in github issue iirc. Either way it is working now. |
🤖 New release
revme: 0.2.0 -> 0.2.1 (✓ API compatible changes)revm: 3.5.0 -> 4.0.0 (revm-interpreter: 1.3.0 -> 2.0.0 (revm-primitives: 1.3.0 -> 2.0.0 (revm-precompile: 2.2.0 -> 3.0.0 (revm-test: 0.1.0revmbreaking changesrevm-interpreterbreaking changesrevm-primitivesbreaking changesrevm-precompilebreaking changesChangelog
revmerevmrevm-interpreterrevm-primitivesrevm-precompilerevm-testThis PR was generated with release-plz.