Bump jenkins-test-harness from 1797.v711534844e8a_ to 1802.v9de0d87365d2 #571
Conversation
Bumps [jenkins-test-harness](https://github.com/jenkinsci/jenkins-test-harness) from 1797.v711534844e8a_ to 1802.v9de0d87365d2. - [Release notes](https://github.com/jenkinsci/jenkins-test-harness/releases) - [Changelog](https://github.com/jenkinsci/jenkins-test-harness/blob/master/docs/CHANGELOG-OLD.md) - [Commits](https://github.com/jenkinsci/jenkins-test-harness/commits) --- updated-dependencies: - dependency-name: org.jenkins-ci.main:jenkins-test-harness dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
|
@jetersen , @jtnord Something weird happens, it seems that 4.43 was released (releases), but not exists in cloudbees Nexus and nothing in artifactory. And as a result PR with version update failed to build. Could you please help? |
|
Not sure who created a release yesterday without deploying it :) Note there is no commit from I don't have permissions to release it. I know @jglick had something in the works for |
|
Well CD is enabled for plugin pom: https://github.com/jenkins-infra/repository-permissions-updater/blob/a64401bf56cdb45c5b994b7d49bc431418adacbc/permissions/pom-plugin.yml#L8 So @timja @jglick any issue with switching Cannot tag core team 😅 |
|
looks like it was me - but I did not run maven-release-plugin and did not even attemot to create a release, I updated the draft release notes for the breaking change but they should still have been in draft :/ At any rate - I can bump the version and release this if needed burning the 4.43 tag. |
|
it is best to change the pull request title or wait with updating the draft till you have published the pom. As changes to the draft could be overwritten when release drafter runs again. I suggest removing the tag and deleting the release as no artifacts was produced. |
ack
if someone has pulled the code then they will have that tag locally causing git to have confusion in the future - tags should really be immutable - releases and version numbers are cheap. I will create a release now and fix the release notes. |
|
tags should be immutable 🤣 say that to GitHub, who suggests I'd argue it is cheap to fix locally if you have a tag that does not match origin. |
|
https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.43.1
yeah if I could prevent that I would :)
Sure, but it is not something you would expect so conforming to the path of least surprise I just moved on and released |
Not supported yet: #462 |
Bumps jenkins-test-harness from 1797.v711534844e8a_ to 1802.v9de0d87365d2.
Release notes
Sourced from jenkins-test-harness's releases.
Commits
Dependabot 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 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)