Skip to content

Verify v4.7.5 merge CI for v4.7/odakyudon - #1

Closed
kyori19 wants to merge 37 commits into
ci/verify-v4.7.5-20261113from
v4.7/odakyudon
Closed

kyori19 wants to merge 37 commits into
ci/verify-v4.7.5-20261113from
v4.7/odakyudon

Conversation

@kyori19

@kyori19 kyori19 commented Nov 12, 2026

Copy link
Copy Markdown
Member

Run GitHub Actions for the existing v4.7.5 merge head. The temporary base is an ancestor of this branch, so verification preserves the exact branch tree. This draft is for CI verification only and will be closed without merging after validation.

diondiondion and others added 30 commits October 5, 2026 15:06
Provide followees-only posts while keeping their audience restricted
|-- R1. Let users publish and recognize followees-only posts
|   |-- Offer unleakable through the Web UI, API, and posting defaults
|   |-- Identify its audience with English and Japanese labels, icons, and guidance
|   `-- Keep replies followees-only unless the posting default requires direct visibility
|-- R2. Restrict access to the author, accounts the author follows, and mentioned accounts
|   |-- Include silent mentions as an independent source of access
|   |-- Apply permissions to individual posts, profile listings, and notifications
|   |-- Deliver to the author and authorized local followers and list owners
|   |-- Apply the same audience rules when merging and regenerating feeds
|   `-- Remove posts from the recipient's home and owned list feeds after the author unfollows them
|       `-- Retain posts still accessible through mentions and preserve other posts
|-- R3. Prevent distribution beyond the intended audience
|   |-- Never federate unleakable posts, including mentions, edits, deletions, poll updates, and inlined quote requests
|   |-- Forbid boosting unleakable posts, including by their author, and hide boost counts
|   `-- Preserve upstream quote permissions and self-quoting without making restricted originals public
|-- R4. Exclude unleakable activity from public counters
|   |-- Exclude unleakable posts from account post totals on creation, deletion, and recounting
|   |-- Exclude unleakable reblogs from original posts' reblog counts on creation and deletion
|   `-- Keep feed regeneration complete when the last posting time excludes these posts
`-- R5. Preserve the visibility values already deployed in the v4.4 fork
    |-- Retain public=0, unlisted=1, private=2, unleakable=3, direct=4, and limited=5
    `-- Preserve direct and limited behavior, including direct-reply notification recognition
Let users identify as cats and display their local posts in cat speech while preserving authored content
|-- R1. Let users manage and expose their account's Cat status
|   |-- Let users enable and disable Cat status through profile settings and the accounts API
|   |   `-- Explain the setting in English and Japanese
|   |-- Persist Cat status per account, defaulting to false
|   `-- Expose Cat status in account API responses and retain it in Web UI account data
|-- R2. Display local Cat posts in cat speech
|   |-- Use the author's current Cat status for post bodies and edit history
|   |-- Convert Japanese and Korean text regardless of the post's language setting
|   |   |-- Convert な to にゃ, ナ to ニャ, and ナ to ニャ
|   |   `-- Convert 나 through 낳 to 냐 through 냫 while preserving the final consonant
|   |-- Preserve URLs, other recognized URIs, hashtags, and mentions
|   `-- Preserve authored text and keep conversion confined to Cat post-body presentation
|       |-- Preserve the stored text and editing source
|       `-- Leave non-Cat posts and other account and post fields unchanged
|-- R3. Exchange Cat status with compatible federated servers without rewriting outgoing posts
|   |-- Publish Cat status as the ActivityPub Actor property isCat
|   |   `-- Define its JSON-LD meaning as as:isCat
|   |-- Retain remote accounts' isCat values, treating a missing value as false
|   `-- Send post content and contentMap without cat-speech conversion
`-- R4. [v4.7 only] Preserve Cat status when upgrading the running v4.4 fork
    |-- Preserve the existing accounts.cat column and every account's stored value
    `-- Retain migration 20181122090024 so applied migrations stay applied
Search stored public post bodies with PGroonga independently of Elasticsearch
|-- R1. Let authenticated users search post bodies through the Web UI and API
|   |-- Search the stored original text, including local and remote posts
|   |-- Require neither Elasticsearch nor authors' search opt-in or prior interaction
|   `-- Expose post search as available in the Web UI
|-- R2. Restrict full-text results to public posts the viewer can see
|   |-- Exclude every non-public visibility, including the viewer's own non-public posts
|   |-- Exclude discarded posts and boost records
|   `-- Preserve upstream permission, block, mute, domain-block and silence filtering
|       `-- Preserve the existing own-post and followed-silenced-author exceptions
|-- R3. Return newest results with usable filtering and pagination
|   |-- Support author selection and exclusive minimum and maximum post IDs
|   |-- Apply offset and limit to results after visibility and account filtering
|   `-- [v4.7 only] Preserve search syntax that can be expressed in SQL
|       |-- Support required terms, excluded terms, quoted phrases and emoji shortcodes
|       |-- Support from, language, has, is and hashtag filters, including negation
|       |-- Support before, after and during with account time zones and Unix milliseconds
|       |-- Restrict in:library to the viewer's public library while retaining in:all and in:public
|       `-- Preserve the v4.7 response shape and bounded database query execution
|-- R4. Provide PGroonga in development and database-backed Ruby CI
|   |-- Use PGroonga-enabled PostgreSQL images for development and Ruby test jobs
|   `-- Keep migration testing on PostgreSQL 14 through 17
`-- R5. [v4.7 only] Preserve deployed PGroonga storage when upgrading the running v4.4 fork
    |-- Retain the existing extension and post-text index without rebuilding them
    |-- Retain migration identities 20190426095531 and 20190426100334
    `-- Keep the schema definition consistent with the deployed extension and index

Validation:
- 97 search parser, transformer, service and API examples pass with Elasticsearch disabled.
- RuboCop passes for all changed Ruby files.
- A v4.4 schema/history upgrade on PostgreSQL 14 retains extension/index OIDs,
  stored text, migration identities and working search, with no pending migrations.
Let users use known accounts' avatars as emojis in posts
|-- R1. Resolve avatar references without custom emoji registration or account discovery
|   |-- Accept :@username: and :@username@domain: in plain text and received HTML
|   |-- Resolve domainless references against the post author's domain
|   |-- Recognize references in bodies, content warnings and poll options
|   `-- Ignore unknown accounts and include each shortcode only once
|-- R2. Display avatars through existing post presentation paths
|   |-- Supply avatar emojis alongside regular custom emojis in post API responses
|   |-- Render them in RSS, administrative views, trend previews and filtered posts
|   |-- Include bodies, content warnings and poll options from edit history
|   |-- Use animated and static avatar images as appropriate
|   |-- Keep avatar emojis out of the picker
|   `-- Support the current Web UI and its separate poll and edit APIs
|       |-- Recognize avatar shortcodes in the current emoji renderer
|       `-- Do not treat avatars as missing entries in the custom emoji endpoint
|-- R3. Preserve avatar notation without mention or translation side effects
|   |-- Do not link, notify or deliver mentions for colon-prefixed account references
|   |-- Keep ordinary mentions followed by a colon recognizable
|   |-- Protect avatar shortcodes during translation of bodies, warnings and polls
|   `-- Keep Web UI character counts consistent with server mention parsing
|       `-- Count avatar references at full length while discounting ordinary remote mentions
`-- R4. Include avatar references in federated posts
    |-- Publish Emoji tags with shortcode names and avatar image URLs
    |-- Preserve authored content and existing mentions, hashtags and custom emoji tags
    `-- Use the standard image serializer and declare the Emoji JSON-LD context
        `-- Preserve tagged collections and quote metadata
Let local users publish richer profiles and longer posts
|-- R1. Let users edit and save profiles with expanded capacity
|   |-- R1.1. Allow up to eight profile fields
|   |   `-- Let users edit all eight fields through the Web UI
|   |-- R1.2. Allow display names up to 64 characters
|   |-- R1.3. Allow profile bios up to 512 counted characters
|   |   `-- Apply the expanded bio limit during onboarding
|   `-- Apply the expanded limits through profile editing and the accounts API
`-- R2. Let users create and edit posts up to 4096 counted characters
    |-- Count the post body and content warning together
    |-- Preserve existing counting rules, including URL and remote mention handling
    `-- Expose the expanded post limit through the instance APIs
        `-- Use that limit for Web UI character counts and submission checks
Keep each post's initial display compact in timelines
`-- R1. Fold long posts earlier
    `-- Use half the upstream height threshold for automatic folding
Let users recognize reply posts consistently in post action bars
`-- R1. Show the reply-all icon for reply posts in ordinary post cards
    |-- Include replies to the author's own posts
    |-- Keep the single-reply icon for posts that are not replies
    `-- Preserve existing reply labels, reply counts, and reply composition behavior
Co-authored-by: Claire <claire.github-309c@sitedethib.com>
Co-authored-by: Claire <claire.github-309c@sitedethib.com>
@kyori19 kyori19 closed this Nov 12, 2026
@kyori19 kyori19 reopened this Nov 12, 2026
@kyori19 kyori19 closed this Nov 12, 2026
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.

9 participants