ci: timestamp-based releases on PR merge#33
Merged
Conversation
…ract Replaces the brief "Plugin System" section with a full "Plugin Architecture" chapter covering the two foundational principles: 1. Data Sovereignty — each SourcePlugin is the sole authority over its own data and has no knowledge of other sources or how its output is joined. All cross-source logic lives exclusively in DataBroker. 2. Download-then-Display — collection (CLI script, credentials, HTTP) and display (SourcePlugin.load(), zero network I/O) are strictly separated. load() raises FileNotFoundError if the local file is absent rather than falling back to a live fetch. Also updates the "Adding a plugin" walkthrough to show the download script step first, corrects config field types (file_path/dir_path replacing path), documents the ICON attribute, and notes that paths persist to data/config.json. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replaces the push-to-main release strategy with a tag-only approach to work within branch protection rules. semantic-release now only computes the next version (--print); the workflow creates and pushes the tag and GitHub release directly without any commit to main. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Drops python-semantic-release entirely. On every PR merge to main, the workflow generates a YYYY.MM.DD tag (with .N suffix if the same date already has a release) and creates a GitHub release with auto-generated notes. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
jschloman
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mainpush: branches: [main]topull_request: types: [closed]withmerged == trueguardpython-semantic-releaseentirely — on each PR merge, the workflow generates a CalVer timestamp tag (vYYYY.MM.DD, with.Nsuffix if that date was already released) and creates a GitHub release with auto-generated notes[tool.semantic_release]config frompyproject.tomlTest plan
v2026.03.31tag + GitHub releasev2026.03.31.1🤖 Generated with Claude Code