Skip to content

Major release: v1.0.0 - #137

Open
mikemadeja wants to merge 4 commits into
mainfrom
develop
Open

mikemadeja wants to merge 4 commits into
mainfrom
develop

Conversation

@mikemadeja

Copy link
Copy Markdown
Owner

Summary

🤖 Generated with Claude Code

mikemadeja and others added 4 commits October 1, 2026 17:04
The auto-release workflow always bumped the patch version on every
develop->main merge, with no way to cut a major or minor release.
Including "major release" or "minor release" (case-insensitive) in
the PR's title now bumps that version component instead, resetting
the components below it to 0. Titles without either phrase keep the
existing patch-bump behavior.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
…tion

ci: support major/minor release bumps via PR title convention
Adds a best-effort, cached check on module import that compares the
installed version against GitHub's latest release and warns if a
newer one exists. Designed to never slow down or break Import-Module:

- Skipped entirely for a dev/source checkout (version 0.0 or 0.0.0,
  depending on whether the module or its manifest was imported), so
  it never fires during this repo's own test suite
- Cached for 24 hours so repeat imports don't hit the network or
  GitHub's rate limit
- Opt-out via $env:PIHOLESHELL_SKIP_UPDATE_CHECK for automation
- GitHub's "latest release" endpoint already excludes the dev-latest
  prerelease build, so that's never mistaken for a real update
- Any failure (network, parsing) is swallowed silently

Co-Authored-By: Claude Sonnet 5 <[email protected]>
feat: warn when a newer PiHoleShell release is available
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant