ghaw: bump choffmeister/git-describe-semver from 0.3.11 to 0.4.0 #1276
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [choffmeister/git-describe-semver](https://github.com/choffmeister/git-describe-semver) from 0.3.11 to 0.4.0. - [Release notes](https://github.com/choffmeister/git-describe-semver/releases) - [Changelog](https://github.com/choffmeister/git-describe-semver/blob/main/.goreleaser.yml) - [Commits](choffmeister/git-describe-semver@v0.3.11...v0.4.0) --- updated-dependencies: - dependency-name: choffmeister/git-describe-semver dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
This PR is on hold until this bug report can be resolved: |
|
No response from the project maintainer(s) yet. Digging into the changes between v0.3.11 and v0.4.0 the biggest difference (at first glance) that might explain the problem appears to be the change from using the Local testing replicates the error. Digging further I find: and reading the notes from that package's maintainer it is clear that support for explicitly setting a boolean flag value as false will not be provided. Projects using this tool are not relying on that behavior, but I was relying on the ability to explicitly set a boolean configuration setting for the GitHub Action as false (which no longer works). Where I'm using the GitHub Action I'll plan to swap to using an explicit Docker container since the GH Action apparently has a different issue (set to use the latest container tag even if you specify an explicit version of the Action to use). |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/github_actions/master/choffmeister/git-describe-semver-0.4.0
branch
Replace the (currently) problematic GitHub Action with a custom job (`git_describe_semver`) that explicitly uses the v0.3.11 version of the Docker container to generate the release asset release version. That version is captured as the job's `version` output which is referenced by other jobs in the build-images and release-build workflows. Those jobs are set as dependent on the `git_describe_semver` job so that they only run after the asset release version is computed. Since the value is computed once at the start of the workflow, I've updated the `actions/checkout` step for each job to use the default checkout option(s) instead of pulling the full repo history each time. This should (somewhat) optimize that step in the build process. refs GH-1276
Replace the (currently) problematic GitHub Action with a custom job (`git_describe_semver`) that explicitly uses the v0.3.11 version of the Docker container to generate the release asset release version. That version is captured as the job's `version` output which is referenced by other jobs in the build-images and release-build workflows. Those jobs are set as dependent on the `git_describe_semver` job so that they only run after the asset release version is computed. Since the value is computed once at the start of the workflow, I've updated the `actions/checkout` step for each job to use the default checkout option(s) instead of pulling the full repo history each time. This should (somewhat) optimize that step in the build process. refs GH-1276
Replace the (currently) problematic GitHub Action with a custom job (`git_describe_semver`) that explicitly uses the v0.3.11 version of the Docker container to generate the release asset release version. That version is captured as the job's `version` output which is referenced by other jobs in the build-images and release-build workflows. Those jobs are set as dependent on the `git_describe_semver` job so that they only run after the asset release version is computed. Since the value is computed once at the start of the workflow, I've updated the `actions/checkout` step for each job to use the default checkout option(s) instead of pulling the full repo history each time. This should (somewhat) optimize that step in the build process. NOTE: Earlier prototype or "scratch" / "testing" jobs and steps are retained in commented out form for future reference. refs GH-1276
Replace the (currently) problematic GitHub Action used in the scheduled monthly image build workflow with a custom job (`git_describe_semver`) that explicitly uses the v0.3.11 version of the Docker container to generate the release asset release version. That version is captured as the job's `version` output which is referenced by the `build_all_images_using_makefile` job in the scheduled-monthly workflow. That job is set as dependent on the `git_describe_semver` job so that they only run after the asset release version is computed. Since the value is computed once at the start of the workflow, I've updated the `actions/checkout` step for the `build_all_images_using_makefile` job to use the default checkout option(s) instead of pulling the full repo history each time. This should (somewhat) optimize that step in the build process. refs GH-1299 refs GH-1276
Bumps choffmeister/git-describe-semver from 0.3.11 to 0.4.0.
Release notes
Sourced from choffmeister/git-describe-semver's releases.
Commits
d2b6ec0Readd next-release support to action (#7)1235d19Fix actionedfdd5cUpdate golang 1.213862bfbfeat: Next release version (#6)cc4b917Support git repository checkouts usinggit worktree(#1) (#5)92b2c9cFix readmee1fa986Improve github actionDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)