Release#1071
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Member
Jenkins BuildsClick to see older builds (150)
|
ceea566 to
65dae93
Compare
65dae93 to
9a3bf07
Compare
9a3bf07 to
17531e1
Compare
17531e1 to
98d9bf0
Compare
98d9bf0 to
00bfdc2
Compare
ca5d802 to
ae28c0f
Compare
ae28c0f to
23696b4
Compare
23696b4 to
527c5a4
Compare
527c5a4 to
757c91f
Compare
757c91f to
714e48c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@status-im/community-dapp@0.1.0
Minor Changes
Patch Changes
wallet@0.2.0
Minor Changes
Patch Changes
@status-im/community-contracts@0.2.0
Minor Changes
api@0.2.3
Patch Changes
get.status.app@0.1.1
Patch Changes
app/get.status.appto umamiapps/get.status.apphub@1.1.1
Patch Changes
portfolio@0.2.3
Patch Changes
status.app@0.1.3
Patch Changes
a535360: feat(status.app): implement i18n coverage across website and admin UI
dc2abfd: fix(status.app): SEO improvements - native App Router sitemap with dynamic blog/help/specs entries, 301 redirects for legacy help/features/renamed URLs, and proper 404 responses for unknown specs/help slugs
86ed961: Update Status app metadata and universal link configuration for the new iOS and Android app details.
4a48bcd: Remove legacy iOS app associations from the AASA file so Status universal links resolve to the new app.
51c1770: feat(status.app): add /learn page surfacing Status Insights posts from Ghost, with sitemap entry, footer link, and i18n messages
9585bda: fix(blog): allow mobile tables to scroll
3e92c15: chore: upgrade next to version 15.5.16 across all projects
551aeb1: feat(status.app): add /feed.xml route and global RSS discovery link for AI crawlers
6b34f46: fix(status.app): fix /brand 500 after Next 15.5 upgrade and harden error boundary
After upgrading to Next.js 15.5.16,
/brandreturned 500 with React error Change community to one with image #130 (Element type is invalid: ... got: undefined). The brand page defined five nested section components asconstarrow functions in the same module as client imports; Next 15.5's RSC bundler no longer resolves those references correctly in production. Section UI is now a dedicated'use client'module (brand-sections.tsx) so Next 15.5's RSC bundler does not treat mixed server/client imports asundefined.JSONLDScriptis imported directly from@status-im/components(not the re-export shim), and the locale route uses explicitexport { default, generateMetadata }only.The root
error.tsxwas also fixed: it importedNotFoundContent, an async Server Component usinggetTranslationsfromnext-intl/server, which broke the error boundary itself and masked the real failure. It now uses a client-only fallback withuseTranslations('error').2c6eea3: Deleting unnecessary ref url "ref=our.status.im"
d624890: self-host
40f0efc: Hide org chart
9c2974b: chore(status.app): remove beta warning on help pages
b3e3155: feat: connect wallet to dApp
20985dc: fix(status.app): style Ghost post tables and reduce blockquote size
9f0fd7d: fix(status.app): remove cloaking signals on get.status.app
b4f9c24: fix(status.app): move platform detection script to root layout
3e9d155: fix(status.app): remove " — Status" suffix from page meta titles
5ae411f: fix job detail page
43b7a23: update copy for banners
d27fc05: fix(status.app): remove "— Status" suffix from blog page titles
a407f80: fix(sitemap): exclude blog tag pages from sitemap
685e3d0: Hide removed get.status.app sections
6c9c8ed: chore: update withdrawal promo
8547cad: add
apps/get.status.appstatus.network@0.2.1
Patch Changes
e2e@0.1.2
Patch Changes
@status-im/status-network@0.1.3
Patch Changes
@status-im/wallet@0.1.3
Patch Changes