You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's still possible to test new versions manually via cloning the branch and manually adding the plugin to Obsidian, but that is less than ideal.
Additional context
BRAT gives developers and beta testers easier access to beta releases of the plugin and should be considered part of the Pull Request review lifecycle prior to merging changes into main and triggering a release.
Follow semver and use a format like X.Y.Z-beta+${COMMIT_SHA}.${WORKFLOW_RUN} for these preview releases.
Notes:
The X.Y.Z semver version should be incremented by the appropriate value for the changes included in this version based on the conventional commit and semantic release standards this repository follows
The workflow run number is useful in case of force pushing or manually re-running a GitHub Action.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
New versions can no longer be installed via BRAT prior to a General Availability release.
Describe the solution you'd like
Implement the
manifest-beta.json
functionality from BRAT into a Preview Release workflow similar to the existing Release workflowDescribe alternatives you've considered
It's still possible to test new versions manually via cloning the branch and manually adding the plugin to Obsidian, but that is less than ideal.
Additional context
BRAT gives developers and beta testers easier access to beta releases of the plugin and should be considered part of the Pull Request review lifecycle prior to merging changes into
main
and triggering a release.Follow semver and use a format like
X.Y.Z-beta+${COMMIT_SHA}.${WORKFLOW_RUN}
for these preview releases.Notes:
X.Y.Z
semver version should be incremented by the appropriate value for the changes included in this version based on the conventional commit and semantic release standards this repository followsThe text was updated successfully, but these errors were encountered: