Comments (15)
This isn't fixed, as can be seen by issues #46 and #47
This shouldn't have been closed, can you please re-open it @mathieudutour ?
from github-tag-action.
@chrisjohnson00 What was the branch you pushed to?
from github-tag-action.
main
from github-tag-action.
@chrisjohnson00 Sorry, cannot reproduce this yet.
Can you also share the workflow? The part where you are using the two actions?
from github-tag-action.
Sure, here you go
name: Create Release
on:
push:
branches: [ 'main' ]
jobs:
create_release:
runs-on: ubuntu-18.04
name: Create Release
steps:
- uses: actions/checkout@v2
- name: Bump version and push tag
id: tag_version
uses: mathieudutour/github-tag-action@v5
with:
github_token: ${{ secrets.REPO_ONLY }}
release_branches: main
default_bump: patch
- name: Create a GitHub release
uses: actions/create-release@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
tag_name: ${{ steps.tag_version.outputs.new_tag }}
release_name: ${{ steps.tag_version.outputs.new_tag }}
body: ${{ steps.tag_version.outputs.changelog }}
The REPO_ONLY
token is used because I need workflows to be triggered from the creation of the tag.
from github-tag-action.
Here's an example where the action fails:
https://github.com/chrisjohnson00/solaredge-prometheus-exporter/actions/runs/388022672
from github-tag-action.
Thanks.
from github-tag-action.
I'm in the same situation. Just upgraded to v5.1 to make use of the new 'custom_release_rules' input. However, no tag is being generated now, therefore the workflow is falling on a subsequent step that requires the new tag name.
from github-tag-action.
Same thing is happening to me. Works on v5
from github-tag-action.
According to mathieu's changelog, the only thing different from v5 is that in the docs he references v5.1.
I can confirm also that v5 works.
from github-tag-action.
According to mathieu's changelog, the only thing different from v5 is that in the docs he references v5.1.
I can confirm also that v5 works.
Yes, but you'll also notice that v5.1
was "released" yesterday, yet this Issue is 9 days old. This means the v5.1
release was deleted and re-created.
from github-tag-action.
no it wasn't, I just forgot to create release but the tag existed.
from github-tag-action.
no it wasn't, I just forgot to create release but the tag existed.
Ahh, I see.
If you treat any merge to your default branch as a release-able event, check out this workflow, it'll do all the release activities.
https://github.com/chrisjohnson00/solaredge-prometheus-exporter/blob/main/.github/workflows/auto-release.yaml
FWIW - It uses a different token for creating the tag, this is to ensure that other flows are triggered, for example to create a latest
and vX.Y.Z
tagged container.
It does require adopting a commit and PR title format, but it's a "standard" convention: https://www.conventionalcommits.org/en/v1.0.0/
from github-tag-action.
This isn't fixed, as can be seen by issues #46 and #47
This shouldn't have been closed, can you please re-open it @mathieudutour ?
And also Dependabot as expected suggested an update to v5.1, which would break any workflow that merges that suggested PR.
from github-tag-action.
This isn't fixed, as can be seen by issues #46 and #47
This shouldn't have been closed, can you please re-open it @mathieudutour ?
@mathieudutour - was this fixed?
from github-tag-action.
Related Issues (20)
- Possibility to customise issueUrlFormat
- how to force push an existed tag ?
- [feature] Rolling release versions
- Set Major. Minor, or Patch Release HOT 2
- Bug: Unable to retrieve commits history when using Squash and Merge on Pull requests
- Help to add suffix non-release tags only
- Add the merged PR #158 to the latest release. HOT 1
- Major bump create bump patch instead HOT 2
- Feature: Support for independent releases in monorepo HOT 5
- PAT setup for github-tag-action HOT 1
- Update action to use Node 20 or newer HOT 4
- Use target-version in a file, then create the tag of both
- Custom tag not being picked up HOT 3
- Use conventionalcommits preset with @semantic-release/commit-analyzer
- SDECE
- contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md
- It produced tons of tags "v0.0.1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-refs-tags-v0-0-1-fix-apicalls2-0-0-0-0-0-0-0-0-0-0-0.0"
- Field `pre_release_branches` isn't applying the tag as pre-release HOT 1
- Still creating new releases when no commits present
- Default value for release_branches unexpectedly matches substring
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 github-tag-action.