Fix Obsidian release publishing - #2
Merged
Merged
Conversation
zorvan
marked this pull request as ready for review
August 4, 2026 14:33
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.
What changed
main.js,manifest.json, andstyles.cssattached in the same operationSetting.setHeading()API for settings section headings!importantdeclaration and replacecolumn-gapwith gridgapWhy
Obsidian rejected release 0.4.5 because the release was published before its required assets were uploaded. The publisher also reported settings-heading and CSS compatibility diagnostics.
The tag-triggered workflow now builds and attests the files before creating the release with those assets, eliminating the asset-upload race.
Validation
npm run verify