Skip to content

chore: release main#395

Draft
elastic-vault-github-plugin-prod[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Draft

chore: release main#395
elastic-vault-github-plugin-prod[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@elastic-vault-github-plugin-prod
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.1

0.2.1 (2026-06-01)

Bug Fixes

  • cli: Show banner on --help to match bare elastic output (#391) (cb4becd)

This PR was generated with Release Please. See documentation.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ COPYPASTE jscpd yes no no 9.13s
✅ REPOSITORY gitleaks yes no no 59.02s
✅ REPOSITORY git_diff yes no no 0.55s
✅ REPOSITORY secretlint yes no no 31.56s
✅ REPOSITORY trivy yes no no 17.66s
✅ TYPESCRIPT eslint 1 0 0 3.43s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod Bot force-pushed the release-please--branches--main branch 3 times, most recently from 4c61d83 to c1ae02b Compare June 1, 2026 18:16
@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod Bot force-pushed the release-please--branches--main branch from c1ae02b to 583eaa0 Compare June 1, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants