Update cloudposse/github-action-auto-release action to v1.18.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-auto-release	action	minor	1.12.0 -> 1.18.1

---

Release Notes

cloudposse/github-action-auto-release (cloudposse/github-action-auto-release)

v1.18.1

Compare Source

🚀 Enhancements

Fix checkout token usage @​goruha (#​34)

what

• Checkout use token

why

• Fix bug with private repos auto release

v1.18.0

Compare Source

Update release-drafter/release-drafter action to v6 @​renovate (#​32)

This PR contains the following updates:

Package	Type	Update	Change
release-drafter/release-drafter	action	major	v5 -> v6

---

Release Notes

release-drafter/release-drafter (release-drafter/release-drafter)

v6

Compare Source

---

Configure Renovate @​renovate (#​1)

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• .github/workflows/auto-release.yml (github-actions)
• .github/workflows/feature-branch.yml (github-actions)
• .github/workflows/main-branch.yaml (github-actions)
• .github/workflows/release.yml (github-actions)
• action.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Update release-drafter/release-drafter action to v6

• Schedule: ["at any time"]
• Branch name: renovate/release-drafter-release-drafter-6.x
• Merge into: main
• Upgrade release-drafter/release-drafter to v6

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Mend Renovate. View repository job log here.

Check for duplicate release @​osterman (#​31)

what

• Release drafter can fail if release already exists.
• Add support for prerelease label (optional)
• Add release job summary

why

• Incorporate fix we have hardcoded in workflows elsewhere

references

• Step does not fail on query failure release-drafter/release-drafter#1313

v1.17.0

Compare Source

• No changes

v1.16.0

Compare Source

• No changes

v1.15.0

Compare Source

• No changes

v1.14.0

Compare Source

• No changes

v1.13.0

Compare Source

Use custom action to get PR info @​goruha (#​30)

what

• Use custom action to get PR info

why

• actions-ecosystem/action-get-merged-pull-request@v1 is not supported.
• Avoid warning about old nodejs version

references

• https://cloudposse.atlassian.net/browse/DEV-956

v1.12.1

Compare Source

pinning version of action call in auto-release-reusable to 1.12.0 @​dylanbannon (#​27)

what

• This is a stable release.
• Pinning auto-release action to v1.12.0 in auto-release-reusable.yml.

why

• This allows users to pin their actions by changing the tag in their copies of auto-release.yml (not auto-release-reusable.yml) to 1.12.1 (not 1.12.0).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13322583	Triggered	MongoDB Credentials	0a1866b	.env	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud