Bump jenkins.version from 2.346.1 to 2.346.3 for bom-2.346.x

[github-actions]

Bump jenkins.version from 2.346.1 to 2.346.3 for bom-2.346.x

Report

Source:
	✔ [jenkins] Get last Jenkins stable version(githubrelease)


Condition:
	✔ [jenkins] Test if Jenkins stable published(maven)

Target:
	✔ [jenkins] Update Jenkins version(shell)

Changelog

Click to expand

Release published on the 2022-08-10 09:36:15 +0000 UTC at the url https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.346.3

# Jenkins 2.346.3

We're excited to announce the release of Jenkins 2.346.3 🎉 

## Changelog and upgrade guide

See the [changelog](https://www.jenkins.io/changelog-stable/#v2.346.3) and [upgrade guide](https://www.jenkins.io/doc/upgrade-guide/2.346/#upgrading-to-jenkins-lts-2-346-3) to learn about breaking changes and other considerations when updating.

## Reporting issues
If you find an issue with this release, please file an issue on [Jira](https://issues.jenkins.io/), otherwise use the [forums](https://community.jenkins.io/) if you're unsure whether you encounter an issue or not.

Remark

This pull request was automatically created using Updatecli.

Please report any issues with this tool here

[basil]

Is this not premature since 2.361.1 won't ship until September 7?

[jetersen]

This version is only used for testing BOM against 2.346.x and due to constraints we are only really testing 2.319.x and weekly.

Hence my wish to run CI for all on GitHub #1350

[jetersen]

You could argue that did not need to merge #1387

[basil]

You could argue that did not need to merge #1387

I think I agree with this.

[basil]

The difference is that merging #1387 early doesn't have any practical side effects as far as I can tell (nobody would be using the bom-2.361 artifact ahead of the LTS release), but merging this PR "early" would have some negative consequences in that the next release of bom-2.346 would start pushing consumers to a .2 contra the documentation.

[jetersen]

effectively this is still 2.346.x and nobody is being pushed to 2.346.2. This is used by sample plugin internally in the bom project not exposed to anybody.

[jetersen]

Feel free to disable auto merge if you disagree.

[basil]

Does this not enable the published bom-2.346 artifact to now contain plugins that depend on 2.346.2, which we don't want to encourage for another month? I do not feel strongly either way.

[jetersen]

Yes potentially this would pick up anyone pointing to .2 plugin that is true.

Again the easiest option would have been to wait merging #1387 as we can easily merge and test on a PR.
I suggest next time we keep it as a draft.

[timja]

Generally plugins that are targeting the next LTS will start to pickup the next bom artifact, we've published it in advance for ages.

No rush for this specific PR though

[jetersen]

@basil I take you still want to wait after 2.361.1 release?
Or are we good with 2.346.3?

[basil]

Since the documentation currently recommends 2.346.1 (and will continue doing so for the next month), I have a slight preference for continuing to deliver that in bom-2.346 throughout the same time period. This is not a strong preference.

[jetersen]

Lets wait, no rush :)

[basil]

Shall we proceed with this now? I think the time has come.