simple-java-mail
simple-java-mail copied to clipboard
Bump info.picocli:picocli from 3.9.0 to 3.9.6
Bumps info.picocli:picocli from 3.9.0 to 3.9.6.
Release notes
Sourced from info.picocli:picocli's releases.
Picocli 3.9.6
Picocli 3.9.6
The picocli community is pleased to announce picocli 3.9.6.
This release improves support for interactive (password) options:
- interactive options can now use type
char[]instead of String, to allow applications to null out the array after use so that sensitive information is no longer resident in memory- interactive options can be optionally interactive if configured with
arity = "0..1"This is the fifty-second public release. Picocli follows semantic versioning.
Table of Contents
New and Noteworthy
This release improves support for interactive (password) options:
- interactive options can now use type
char[]instead of String, to allow applications to null out the array after use so that sensitive information is no longer resident in memory- interactive options can be optionally interactive if configured with
arity = "0..1"For example, if an application has these options:
@Option(names = "--user") String user;
@Option(names = "--password", arity = "0..1", interactive = true) char[] password;With the following input, the
passwordfield will be initialized to"123"without prompting the user for input:--password 123 --user JoeHowever, if the password is not specified, the user will be prompted to enter a value. In the following example, the password option has no parameter, so the user will be prompted to type in a value on the console:
--password --user JoeFixed issues
- #657 Support type
char[]for interactive options. Thanks to Lukáš Petrovický for raising this issue.
... (truncated)
Changelog
Sourced from info.picocli:picocli's changelog.
Picocli 3.9.6
The picocli community is pleased to announce picocli 3.9.6.
This release improves support for interactive (password) options:
- interactive options can now use type
char[]instead of String, to allow applications to null out the array after use so that sensitive information is no longer resident in memory- interactive options can be optionally interactive if configured with
arity = "0..1"This is the fifty-second public release. Picocli follows semantic versioning.
Table of Contents
New and Noteworthy
This release improves support for interactive (password) options:
- interactive options can now use type
char[]instead of String, to allow applications to null out the array after use so that sensitive information is no longer resident in memory- interactive options can be optionally interactive if configured with
arity = "0..1"For example, if an application has these options:
@Option(names = "--user") String user;
@Option(names = "--password", arity = "0..1", interactive = true) char[] password;With the following input, the
passwordfield will be initialized to"123"without prompting the user for input:--password 123 --user JoeHowever, if the password is not specified, the user will be prompted to enter a value. In the following example, the password option has no parameter, so the user will be prompted to type in a value on the console:
--password --user JoeFixed issues
- #657 Support type
char[]for interactive options. Thanks to Lukáš Petrovický for raising this issue.- #536 Support optionally interactive options. Thanks to Lukas Heumos for raising this issue.
... (truncated)
Commits
1bf2c26Release picocli version 3.9.6665ba07DOC update release notes for 3.9.63daa7c4#536 DOC fix: default arity for interactive options is zerobbdea1b#657 bugfix1be1a2f#657 handleList\<char[]>generic types correctly; add RELEASE-NOTES entry3355304#536#657 optionally interactive options and interactive options of type `...e1b9622Update index.adoc963f015DOC add man/3.x documentation directoryd4d596dChange % to %% when using ${DEFAULT-VALUE} in option description9735930DOC: add example for interactive password alternatives- Additional commits viewable in compare view
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 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)