Skip to content

Support rich messages, topic read state, and automatic releases - #11

Closed
AbdulKus wants to merge 0 commit into
mainfrom
feature/rich-messages-topic-read-release
Closed

Support rich messages, topic read state, and automatic releases#11
AbdulKus wants to merge 0 commit into
mainfrom
feature/rich-messages-topic-read-release

Conversation

@AbdulKus

@AbdulKus AbdulKus commented Aug 9, 2026

Copy link
Copy Markdown
Owner

Что изменено

  • добавлено отображение messageRichMessage: превью в чате и списке, полное содержимое через встроенный Instant View
  • поддержаны новые блоки/форматирование, custom emoji и текстовое отображение формул
  • перед переключением топика сохраняются прочтение и позиция прокрутки
  • успешная сборка main автоматически создаёт GitHub Release с APK и SHA256SUMS.txt
  • добавлены английская и русская локализации

Проверка

  • git diff --check
  • XML и YAML синтаксически проверены
  • полная Android-сборка запускается GitHub Actions

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread .github/workflows/android.yml Outdated
path: artifacts

- name: Publish Frogram X release
uses: softprops/action-gh-release@v2

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant