Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
v6.52.0
2923efbf Merge tag 'v6.52.0'
by Jannis Fed...
Succeeded
main
2923efbf Merge tag 'v6.52.0'
by Jannis Fed...
Succeeded
main
1ad8fdfa ✨ Added tax ID collection to Stripe checkout when automatic tax is enabled (#24682) no ref Note: This feature is still in beta. Enables tax ID input field in Stripe checkout sessions when the `stripeAutomaticTax` feature flag is enabled. This allows for proper tax compliance and tax ID collection during subscription and donation checkout flows.
by Jannis Fed...
Succeeded
24682
c6f6ee6f ✨ Added tax ID collection to Stripe checkout when automatic tax is enabled no ref - enables tax_id_collection on the subscription, donation, and gift checkout sessions when the stripeAutomaticTax flag is on, so customers can enter a VAT/tax ID for proper tax compliance - centralised the automatic-tax session options behind a single _applyAutomaticTaxSessionOptions helper to remove the duplicated customer_update logic across the three checkout flows - customer_update now syncs both address and name so Stripe keeps the customer's tax record accurate
by Jannis Fed...
Succeeded
v6.51.0
16a02c92 Merge tag 'v6.51.0'
by Jannis Fed...
Succeeded
main
16a02c92 Merge tag 'v6.51.0'
by Jannis Fed...
Succeeded
v6.50.0
35b03b5e [magicpages] Fixed production Docker build after better-sqlite3 migration - v6.50.0 switched ghost/core from the sqlite3 package to better-sqlite3, but the fork-specific production/Dockerfile still rebuilt the now-removed sqlite3 native binding (cd node_modules/sqlite3 && npm run install) - the merge only updated upstream's Dockerfile.production, not our separate production/Dockerfile, so the Build and Push Docker Image workflow failed with "cd: can't cd to node_modules/sqlite3" - point the manual native rebuild at better-sqlite3, matching upstream's Dockerfile.production
by Jannis Fed...
Succeeded
main
35b03b5e [magicpages] Fixed production Docker build after better-sqlite3 migration - v6.50.0 switched ghost/core from the sqlite3 package to better-sqlite3, but the fork-specific production/Dockerfile still rebuilt the now-removed sqlite3 native binding (cd node_modules/sqlite3 && npm run install) - the merge only updated upstream's Dockerfile.production, not our separate production/Dockerfile, so the Build and Push Docker Image workflow failed with "cd: can't cd to node_modules/sqlite3" - point the manual native rebuild at better-sqlite3, matching upstream's Dockerfile.production
by Jannis Fed...
Succeeded
v6.50.0
7d57261c Merge pull request #238 from magicpages/develop v6.50.0
by Jannis Fed...
Succeeded
main
7d57261c Merge pull request #238 from magicpages/develop v6.50.0
by Jannis Fed...
Succeeded
develop
a172ee83 [magicpages] Implement DMARC alignment checks for email addresses in EmailAddressService
by Jannis Fed...
Succeeded
main
8cd1e9c2 🐛 Fixed admin sidebar hidden behind legacy screens on mobile (#28956) no ref On mobile, opening the sidebar from a legacy Ember screen (e.g. the billing/Ghost(Pro) screen) appeared to do nothing — the sidebar drawer opened in the DOM but was painted behind the screen content. Legacy Ember screens use very high z-index values (the billing overlay is z-index: 9999) and none of the Ember host's ancestors establish a stacking context, so those z-indexes compete in the root stacking context and paint over the React shell's mobile sidebar drawer (z-50), which is portalled to <body>. Isolating #ember-app into its own stacking context keeps those legacy z-indexes scoped to the Ember content region, so the shell's sidebar drawer renders above it as expected. Fullscreen Ember screens are unaffected — they hide the sidebar via sidebar visibility, not z-index.
by Jannis Fed...
Succeeded
28956
44916b13 🐛 Fixed admin sidebar hidden behind legacy screens on mobile On mobile, opening the sidebar from a legacy Ember screen (e.g. the billing/Ghost(Pro) screen) appeared to do nothing — the sidebar drawer opened in the DOM but was painted behind the screen content. Legacy Ember screens use very high z-index values (the billing overlay is z-index: 9999) and none of the Ember host's ancestors establish a stacking context, so those z-indexes compete in the root stacking context and paint over the React shell's mobile sidebar drawer (z-50), which is portalled to <body>. Isolating #ember-app into its own stacking context keeps those legacy z-indexes scoped to the Ember content region, so the shell's sidebar drawer renders above it as expected. Fullscreen Ember screens are unaffected — they hide the sidebar via sidebar visibility, not z-index.
by Jannis Fed...
Succeeded
v6.49.0
fa5a2c59 Merge pull request #237 from magicpages/develop v6.49.0
by Jannis Fed...
Succeeded
main
fa5a2c59 Merge pull request #237 from magicpages/develop v6.49.0
by Jannis Fed...
Succeeded
develop
5b28272e Merge tag 'v6.49.0' into develop
by Jannis Fed...
Succeeded
v6.48.0
cc685894 Merge pull request #236 from magicpages/develop v6.48.0
by Jannis Fed...
Succeeded
main
cc685894 Merge pull request #236 from magicpages/develop v6.48.0
by Jannis Fed...
Succeeded
develop
0e6bf328 Merge tag 'v6.48.0' into develop
by Jannis Fed...
Succeeded
v6.47.0
4809d7e8 Merge pull request #235 from magicpages/develop v6.47.0
by Jannis Fed...