Skip to content

Conversation

@liblaf
Copy link
Contributor

@liblaf liblaf bot commented Aug 31, 2025

🤖 I have created a release beep boop

0.3.3 (2025-09-03)

🐛 Bug Fixes

  • deps: update rust crate clap to v4.5.47 (#26) (26a8a87)
  • deps: update rust crate grapes to v0.2.2 (#25) (9cc148a)
  • deps: update rust crate tracing-subscriber to v0.3.20 [security] (#23) (5ab440d)

This PR was generated with Release Please. See documentation.

@liblaf liblaf bot added automerge autorelease: pending is the initial state of the Release PR before it is merged labels Aug 31, 2025
@liblaf
Copy link
Contributor Author

liblaf bot commented Aug 31, 2025

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ BASH shellcheck 2 0 0 0.28s
✅ BASH shfmt 2 0 0 0 0.02s
✅ COPYPASTE jscpd yes no no 1.71s
✅ JSON jsonlint 8 0 0 0.15s
✅ JSON prettier 8 0 0 0 0.34s
✅ JSON v8r 8 0 0 4.39s
⚠️ MARKDOWN markdownlint 3 0 11 0 0.7s
⚠️ SPELL cspell 19 14 0 3.37s
✅ YAML prettier 2 0 0 0 0.39s
✅ YAML v8r 2 0 0 4.07s
✅ YAML yamllint 2 0 0 0.36s

Detailed Issues

⚠️ SPELL / cspell - 14 errors
completions/bash/tangerine:7:32      - Unknown word (CWORD)      -- cur="${COMP_WORDS[COMP_CWORD]}"
	 Suggestions: [CORD, CHORD, COORD, WORD, DWORD]
completions/bash/tangerine:13:38     - Unknown word (CWORD)      -- COMP_WORDS[@]:0:COMP_CWORD}"
	 Suggestions: [CORD, CHORD, COORD, WORD, DWORD]
completions/bash/tangerine:39:9      - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/bash/tangerine:45:42     - Unknown word (CWORD)      -- cur} == -* || ${COMP_CWORD} -eq 1 ]] ; then
	 Suggestions: [CORD, CHORD, COORD, WORD, DWORD]
completions/bash/tangerine:61:13     - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/bash/tangerine:67:42     - Unknown word (CWORD)      -- cur} == -* || ${COMP_CWORD} -eq 2 ]] ; then
	 Suggestions: [CORD, CHORD, COORD, WORD, DWORD]
completions/bash/tangerine:75:13     - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/bash/tangerine:81:42     - Unknown word (CWORD)      -- cur} == -* || ${COMP_CWORD} -eq 2 ]] ; then
	 Suggestions: [CORD, CHORD, COORD, WORD, DWORD]
completions/bash/tangerine:89:13     - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/bash/tangerine:103:13    - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/zsh/_tangerine:85:9      - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/zsh/_tangerine:87:1      - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/zsh/_tangerine:89:9      - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
completions/zsh/_tangerine:91:1      - Unknown word (esac)       -- esac
	 Suggestions: [esau, Esau, esa, esc, ESA]
CSpell: Files checked: 16, Issues found: 14 in 2 files.


You can skip this misspellings by defining the following .cspell.json file at the root of your repository
Of course, please correct real typos before :)

{
    "version": "0.2",
    "language": "en",
    "ignorePaths": [
        "**/node_modules/**",
        "**/vscode-extension/**",
        "**/.git/**",
        "**/.pnpm-lock.json",
        ".vscode",
        "package-lock.json",
        "megalinter-reports"
    ],
    "words": [
        "CWORD",
        "esac"
    ]
}


You can also copy-paste megalinter-reports/LINTER_DEFAULT at the root of your repository
⚠️ MARKDOWN / markdownlint - 11 errors
CHANGELOG.md:18 MD024/no-duplicate-heading Multiple headings with the same content [Context: "⬆️ Dependencies"]
CHANGELOG.md:27 MD024/no-duplicate-heading Multiple headings with the same content [Context: "⬆️ Dependencies"]
CHANGELOG.md:37 MD024/no-duplicate-heading Multiple headings with the same content [Context: "⬆️ Dependencies"]
CHANGELOG.md:52 MD024/no-duplicate-heading Multiple headings with the same content [Context: "❤️ New Contributors"]
CHANGELOG.md:58 MD024/no-duplicate-heading Multiple headings with the same content [Context: "💥 BREAKING CHANGES"]
CHANGELOG.md:66 MD024/no-duplicate-heading Multiple headings with the same content [Context: "♻ Code Refactoring"]
CHANGELOG.md:74 MD024/no-duplicate-heading Multiple headings with the same content [Context: "🔧 Continuous Integration"]
CHANGELOG.md:80 MD024/no-duplicate-heading Multiple headings with the same content [Context: "❤️ New Contributors"]
docs/help.md:17 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h3; Actual: h6]
docs/help.md:42 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h3; Actual: h6]
docs/help.md:42 MD024/no-duplicate-heading Multiple headings with the same content [Context: "**Arguments:**"]

See detailed reports in MegaLinter artifacts

MegaLinter is graciously provided by OX Security

@liblaf liblaf bot force-pushed the release-please--branches--main--components--tangerine branch 3 times, most recently from 74c4e71 to 21604fb Compare September 2, 2025 17:41
@liblaf liblaf bot force-pushed the release-please--branches--main--components--tangerine branch from ff2f723 to fbc339e Compare September 3, 2025 09:30
@mergery mergery bot merged commit c27323f into main Sep 7, 2025
22 checks passed
@mergery mergery bot deleted the release-please--branches--main--components--tangerine branch September 7, 2025 01:23
@liblaf
Copy link
Contributor Author

liblaf bot commented Sep 7, 2025

🤖 Created releases:

🌻

@liblaf liblaf bot added autorelease: tagged means that the Release PR has been merged and the release has been tagged in GitHub and removed autorelease: pending is the initial state of the Release PR before it is merged labels Sep 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged means that the Release PR has been merged and the release has been tagged in GitHub

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants