Comments (5)
Please see https://github.com/release-it/release-it?tab=readme-ov-file#troubleshooting--debugging and use verbose and debugging options to better see what's going on.
from release-it.
@webpro Ok, I've removed all the tags from my repo and started again, here is the output from scenario:
- run Action that creates release - v6.0.0
- push 3 commits,
- run action that creates release v6.0.1
Run npx release-it v[6](https://github.com/placzkowskim/xx).0.1 --ci -VV
$ git diff --quiet HEAD
$ git rev-parse --abbrev-ref HEAD
main
$ git config --get branch.main.remote
origin
$ git remote get-url origin
https://github.com/xx
$ git fetch
$ git rev-parse --abbrev-ref HEAD [cached]
$ git describe --tags --match=* --abbrev=0
fatal: No names found, cannot describe anything.
$ git symbolic-ref HEAD
refs/heads/main
$ git for-each-ref --format="%(upstream:short)" refs/heads/main
origin/main
$ git rev-parse --abbrev-ref HEAD [cached]
$ git config --get branch.main.remote [cached]
$ git remote get-url origin [cached]
$ git fetch [cached]
$ git rev-parse --abbrev-ref HEAD [cached]
$ git describe --tags --match=* --abbrev=0 [cached]
$ git log --pretty=format:"* %s (%h)"
* Commit message test 3. (d[7](https://github.com/xx)
🚀 Let's release realase-test (6.0.0...v6.0.1)
Changelog:
* Commit message test 3. (d7453a7)
$ npm version v6.0.1 --no-git-tag-version
v6.0.1
$ git status --short --untracked-files=no
M package-lock.json
M package.json
Changeset:
M package-lock.json
M package.json
$ git add . --update
$ git commit --message release v6.0.1
[main 24103[9](https://github.com/xx] release v6.0.1
2 files changed, 3 insertions(+), 3 deletions(-)
$ git tag --annotate --message Release v6.0.1 v6.0.1
$ git symbolic-ref HEAD [cached]
$ git for-each-ref --format="%(upstream:short)" refs/heads/main [cached]
$ git push --follow-tags
! octokit repos.createRelease "Release v6.0.1" (v6.0.1)
octokit repos.createRelease: done (https://api.github.com/repos/xx)
🔗 https://github.com/xx
🏁 Done (in 2s.)
It looks like there are no tags ?? In github I can see those two, as well as in my SourceTree, I dont know what is going on now :/
from release-it.
may set checkout deep = 0?
from release-it.
Yes, you need to set the workflow checkout job fetch-depth: 0
- uses: actions/checkout@v4
with:
fetch-depth: 0
from release-it.
I've already tried this and still output is the same. Here is updated action code :
name: Relase-it
on:
workflow_dispatch:
inputs:
releaseversion:
description: "pass release version in v*.*.* format"
required: true
type: string
jobs:
release:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-dept: 0
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: 20.8.1
- name: Install dependencies
run: npm ci
- name: End message
run: echo 'Dependencies installed'
- name: Initialize Git User
run: |
git config --global user.email "[email protected]"
git config --global user.name "Release Workflow"
- name: Run release
run: npx release-it ${{github.event.inputs.releaseversion}} --ci -VV
env:
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
from release-it.
Related Issues (20)
- Release-it picks up wrong release number. HOT 8
- Bug - Issue with github comment on resolved items HOT 10
- [ERROR] GitLab CI error on NPM notice HOT 2
- Cannot understand how release verison is calculated HOT 2
- Hook for after changelog is written to CHANGELOG.md? HOT 2
- Bug: Error when rolling back git tag release suppresses original error
- Error Invalid version HOT 7
- beta and alpha releases do not work HOT 7
- When publishing an npm package, when the publishPath option is set, isCollaborator should detect package.json under publishPath instead of the current directory. HOT 2
- Wrong documentation related to running a custom Git Push command HOT 4
- How can I change method of releasing (from "Release 0.0.1" to "v0.0.1") ? HOT 3
- How can I change parametrs from "Release 0.0.0" to "v0.0.0" after writing release-it, and publishing into repository ? HOT 7
- Return different message when requireCommitsFail is false HOT 1
- Commits to one dir generate release of another. HOT 2
- Programatic Usage: Release-Version Premature Exit HOT 1
- Can't quite get auto-changelog right in github release notes. githubRelease runs before git commit/tag HOT 8
- Can't upload github release assets without rewriting release's changelog HOT 2
- Error 405 (Method Not Allowed) when creating Gitlab release (Gitlab self-hosted) HOT 2
- Is it possible to ignore `git.requireBranch` when releasing a pre-release only? HOT 2
- Run the script without prompts (accept all defaults) HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release-it.