[JIRA] (JENKINS-60908) AWS Secrets Manager Plugin Breaking Change

[chris+jenk...@chriskilding.com (JIRA)]

Title: Message Title

Chris Kilding commented on JENKINS-60908   Re: AWS Secrets Manager Plugin Breaking Change Hi Ethan, could you clarify the last sentence? Not quite sure what it means, but there might be something worth investigating in it. You are correct that it’s a breaking change. I kept the previous auto-detection strategy going as long as I could, but unfortunately the multi-type credential object this entailed broke fundamental assumptions of important credential consumers, like the Git plugin. So it was a tough call but I had to change it. I’ll add a doc notice as you suggest. The only in-band mechanism Jenkins currently provides to announce a breaking change is the plugin version number. However per the Semantic Versioning standard, this only really works if you are post version 1 (when you can indicate a breaking change with a major version increment). Therefore I intend to finish the last 2 or 3 minor changes I’m working on, sit on it for a while, then if all looks good release stable version 1.0.0. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204299.1580318008000.8392.1580319720136%40Atlassian.JIRA.