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
Now that releases can be automatically published to github (when enable-github-release: true), it would be useful if we could also generate a PR that creates an update to update.json when the release is published.
This would avoid the additional manual step of creating the PR.
Another option would be that I could create a github action for the repository, but it seems it might be better integrated into the existing CI.
The requirements would be:
When a release is published to the repository, update the "version" and "update_link" fields in the update.json file.
Now that releases can be automatically published to github (when
enable-github-release: true
), it would be useful if we could also generate a PR that creates an update toupdate.json
when the release is published.This would avoid the additional manual step of creating the PR.
Another option would be that I could create a github action for the repository, but it seems it might be better integrated into the existing CI.
The requirements would be:
strict_max_version
- it isn't used at the moment, but might be in the future (xref https://extensionworkshop.com/documentation/manage/updating-your-extension/).I'm suggesting to create a PR, so that the authors can do a final check before the add-on is released to everyone.
The text was updated successfully, but these errors were encountered: