chore: release 1.1.2 (authorUrl → author profile)#8
Merged
Conversation
Point manifest.authorUrl at the author profile (https://github.com/Post-Math) instead of the plugin repo, per the Obsidian community-plugin submission guidelines. Metadata-only; no functional change. Bumps to 1.1.2 so the release the directory bot inspects carries the corrected manifest. - manifest.json: authorUrl, version 1.1.1 -> 1.1.2 - versions.json: add "1.1.2": "1.0.0" - CHANGELOG.md: 1.1.2 section Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
Prep release 1.1.2 — a metadata-only fix ahead of the Obsidian community
plugin submission.
manifest.json:authorUrlnow points to the author profile(
https://github.com/Post-Math) instead of the plugin repo — the directoryvalidation bot flags
authorUrlpointing at the plugin repository. Versionbumped
1.1.1 → 1.1.2.versions.json: add"1.1.2": "1.0.0".CHANGELOG.md:1.1.2section.No plugin code / behavior change.
Release flow
After this merges to
dev, adev → mainrelease PR (templaterelease.md)will auto-tag
1.1.2and publish the release on merge — the first real run ofthe automatic pipeline.
Type of change
main.js/styles.csschange)Checklist
manifest.jsonversion = 1.1.2versions.jsonhas"1.1.2": "1.0.0"CHANGELOG.mdhas a dated## [1.1.2]sectionnode scripts/validate.mjspasses