Support rich messages, topic read state, and automatic releases - #11
Support rich messages, topic read state, and automatic releases#11AbdulKus wants to merge 0 commit into
Conversation
a7ccbea to
51f4007
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a7ccbea4c6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| path: artifacts | ||
|
|
||
| - name: Publish Frogram X release | ||
| uses: softprops/action-gh-release@v2 |
There was a problem hiding this comment.
Block releases signed with the ephemeral key
When any signing secret is missing, the Prepare API credentials and signing step deliberately generates a new development keystore (lines 82–100), but this job still publishes that APK as the latest GitHub release. Such an APK cannot upgrade installations signed by the real release key, and users who install it cannot upgrade to a later properly signed build. Require the persistent signing credentials—or otherwise prevent the release job from running—before publishing this artifact.
Useful? React with 👍 / 👎.
Что изменено
messageRichMessage: превью в чате и списке, полное содержимое через встроенный Instant Viewmainавтоматически создаёт GitHub Release с APK иSHA256SUMS.txtПроверка
git diff --check