3705 Commits

Author SHA1 Message Date
postiz-contribution[bot]
a87826d44a
Merge main into staging 2026-10-15 20:08:33 +00:00
Nevo David
08b1e6b46f Merge remote-tracking branch 'origin/main' 2026-10-15 22:23:33 +03:00
Nevo David
20609d33a0 feat: hubspot integration 2026-10-15 22:23:09 +03:00
postiz-contribution[bot]
4ff903d899
Merge main into staging 2026-10-15 14:08:26 +00:00
Gilad Resisi
021c2ee076
Merge pull request #2266 from gitroomhq/feat/self-host-plus-jakarta-sans
fix(frontend): self-host Plus Jakarta Sans instead of next/font/google
2026-10-15 11:36:47 +00:00
Nevo David
adb8a1a7b2
Merge pull request #2269 from gitroomhq/fix/return-url-same-origin
fix(auth): only follow a returnUrl on this app after signing in
2026-10-15 13:55:39 +03:00
Nevo David
6634bb7e06
Merge pull request #2267 from gitroomhq/feat/hubspot-installed-modal
feat(hubspot): explain the HubSpot install on the calendar
2026-10-15 13:55:15 +03:00
Nevo David
9a88959839 fix(auth): only follow a returnUrl on this app after signing in
ReturnUrlComponent stored ?returnUrl= whenever it contained "http", and
layout.context sent the browser there after login or sign-up. That made the
login an open redirect, and a javascript: value could run script on the
Postiz origin. returnUrl is now kept only when it is an http(s) address on
the app's own origin, checked when it is stored and again when it is read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 13:49:26 +03:00
Nevo David
ef8c7b8c44 feat(hubspot): explain the HubSpot install on the calendar
The HubSpot app's redirect URL (/oauth/hubspot/callback) dropped people on
the bare calendar, so nothing said the install worked or what to do next.
It now lands on /launches?hubspot=installed, where HubspotInstalled opens a
modal with the next steps in HubSpot (Agent Builder > MCP Servers > Postiz
MCP) and then clears the param. returnUrl brings someone who has to sign in
first back to it. Two new strings in en and the 14 Lingo locales.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 13:40:07 +03:00
Nevo David
0956d49ab7 feat: hubspot 2026-10-15 12:53:26 +03:00
Gilad Resisi
ea9c820160 fix(frontend): self-host Plus Jakarta Sans instead of next/font/google
The frontend build fetched Plus Jakarta Sans from Google Fonts at build
time, and a few CI builds failed with "Can't resolve
'@vercel/turbopack-next/internal/font/google/font'". The font is now
loaded with next/font/local from woff2 files in the repo, so the build
no longer depends on Google.

The files are the variable fonts from tokotype/PlusJakartaSans commit
18d1cd2f (the same files google/fonts ships, SIL OFL 1.1, license
included), converted to woff2. All four layouts share one 500-700
upright + italic definition.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 16:35:27 +07:00
claude[bot]
4e999f931d Merge remote-tracking branch 'origin/main' into staging
Resolved-by: claude-code-action

# Conflicts:
#	.env.example
2026-10-15 09:26:27 +00:00
Nevo David
d758146320 Merge remote-tracking branch 'origin/main' 2026-10-15 12:14:46 +03:00
Gilad Resisi
f4628143f6
Merge pull request #2265 from gitroomhq/fix/facebook-video-insights-metric
fix(facebook): stop requesting total_video_impressions in video post analytics
2026-10-15 09:04:06 +00:00
Gilad Resisi
b64b2c0048 fix(facebook): stop requesting total_video_impressions in video post analytics
Since early October the Graph API rejects total_video_impressions on the
video_insights edge with "(#100) The value must be a valid insights
metric", on reels and feed videos alike and on every API version. The
metric is requested together with the others in one call, so the whole
request fails and videoPostAnalytics returns [] for every Facebook video
and reel post. Production logs show 100+ such rejections per hour.

Drop the metric and its Impressions case; the remaining metrics
(total_video_views, total_video_reactions_by_type_total and the reels
ones) are still accepted individually and together.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-15 15:58:43 +07:00
claude[bot]
94830e692b Merge remote-tracking branch 'origin/main' into staging
Resolved-by: claude-code-action

# Conflicts:
#	libraries/nestjs-libraries/src/integrations/social/pinterest.provider.ts
2026-10-15 08:52:52 +00:00
Gilad Resisi
ba8cb48143
Merge pull request #2263 from gitroomhq/fix/pinterest-transient-error-main
fix(pinterest): retry transient 'Something went wrong on our end' errors
2026-10-15 08:44:07 +00:00
Gilad Resisi
fc29b82590
Merge pull request #2264 from gitroomhq/fix/vk-api-domain-ru
fix(vk): call VK ID and VK API on the vk.ru domains
2026-10-15 08:36:37 +00:00
Gilad Resisi
5a5da1aed4 fix(vk): call VK ID and VK API on the vk.ru domains
VK asked integrations to move from the vk.com hosts to vk.ru
(api.vk.ru, id.vk.ru) by 2025-09-30. Switch the authorize, token,
user_info and API method URLs; the post releaseURL links stay on vk.com.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 15:29:29 +07:00
postiz-contribution[bot]
cc7b79d45f
Merge main into staging 2026-10-15 08:08:17 +00:00
Gilad Resisi
a7666b5e2b
Merge pull request #2258 from gitroomhq/fix/youtube-thumbnail-keep-release-url-main
fix(youtube): keep the video id and URL on a post that fails only at the thumbnail step
2026-10-15 07:37:52 +00:00
Gilad Resisi
304538bbac
Merge pull request #2235 from gitroomhq/mastra-protocol-update
fix(mcp): serve the streamable endpoints in Mastra's dual-era mode
2026-10-15 07:31:00 +00:00
Gilad Resisi
3168c1e148
Merge branch 'main' into fix/pinterest-transient-error-main 2026-10-15 12:47:33 +07:00
Gilad Resisi
18a312b6ba fix(pinterest): retry transient 'Something went wrong on our end' errors
Pinterest's pin creation endpoint intermittently answers with
{"code":2787,"message":"Sorry! Something went wrong on our end."}.
It was unmapped in handleErrors, so the post failed immediately as a
non-retryable BadBody with the 'Unknown Error' placeholder, even though
identical requests succeed minutes later.

Map it to a retry (3 attempts, 5s apart) with a curated message so a
short Pinterest hiccup no longer fails the post, and if it persists the
user sees what actually happened instead of 'Unknown Error'.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-10-15 12:33:46 +07:00
Gilad Resisi
05e8efb972
Merge pull request #2262 from gitroomhq/fix/telegram-connect-input-readonly
fix(telegram): mark connect command input as read-only
2026-10-15 05:29:24 +00:00
Gilad Resisi
388da50112
Merge pull request #2261 from gitroomhq/fix/instagram-media-fetch-retryable-main
fix(instagram): make 'Media fetch failed' (2207052) retryable
2026-10-15 05:20:00 +00:00
Gilad Resisi
aff38f99e6 fix(telegram): mark connect command input as read-only
The connect command input had a controlled value without onChange,
which made React log a console error when opening the Telegram
connect modal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 12:19:38 +07:00
Nevo David
7ca9c39ce6 Merge branch 'main' into feat/hubspot-mcp-oauth 2026-10-15 08:09:24 +03:00
Gilad Resisi
b95e1e2cb4 fix(instagram): make media fetch failed (2207052) retryable
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-10-15 12:05:19 +07:00
Gilad Resisi
cefb5e7c86
Merge pull request #2260 from gitroomhq/fix/instagram-collaborator-error-main
fix(instagram): report untaggable collaborators instead of "Unknown Error"
2026-10-15 04:24:46 +00:00
Gilad Resisi
c1fd5cffbe fix(instagram): report untaggable collaborators instead of "Unknown Error"
Instagram rejects a media container when a collaborator handle cannot be
tagged, with error_subcode 2207018 ("Invalid user id"). handleErrors had no
branch for it, so it fell through to the generic BadBody fallback and the
customer's failure email read "An error occurred while posting to Instagram:
Unknown Error", with nothing pointing at the collaborator tag.

Map 2207018 to a bad-body message naming the three real causes: wrong handle,
private account, or collaborator invites disabled. instagram.standalone
delegates to this handleErrors, so both channel types are covered.

Meta's own error_user_msg is not surfaced instead: it comes back localized to
the connected account's language (Hebrew, in the reproduction), so it is not
usable as user-facing text.

Verified against a live Instagram channel by creating a media container with
the customer's exact handle: pre-fix "Unknown Error", post-fix the new message.
2026-10-15 10:19:44 +07:00
claude[bot]
ee191ec210 Merge remote-tracking branch 'origin/main' into staging
Resolved-by: claude-code-action

# Conflicts:
#	libraries/nestjs-libraries/src/integrations/social/youtube.provider.ts
2026-10-15 02:58:07 +00:00
Gilad Resisi
0c93578825
Merge pull request #2257 from gitroomhq/fix/youtube-thumbnail-verify-message-main
fix(youtube): clarify unverified-channel thumbnail error message
2026-10-15 02:50:26 +00:00
Gilad Resisi
23beddcd09 fix(youtube): keep the video id and URL on a post that fails only at the thumbnail step
The video is already live when thumbnails.set is rejected, but the post
ended in ERROR with no release URL, so users re-uploaded duplicates. The
provider now throws PublishedWithError with the video id and URL; the post
activity persists them through PostsService.updateResolvedRelease (the
existing org-scoped repository write, state untouched) and rethrows
BadBody, so every workflow version still marks the post ERROR while the
calendar can link to the live video.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 09:40:09 +07:00
Gilad Resisi
afdd37c11e
Merge pull request #2256 from gitroomhq/fix/instagram-comment-not-added
fix(instagram): map the rejected comment error 1772107 to a readable message
2026-10-15 02:26:46 +00:00
Gilad Resisi
b2897ff7d9 fix(youtube): clarify unverified-channel thumbnail error message
The youtube.thumbnail error mapping said 'Your account is not verified',
which customers read as their Postiz account/channel connection - one
customer disconnected and re-added their YouTube channel trying to fix
it. The video is actually live on YouTube in this scenario; only the
thumbnails.set call is rejected because custom thumbnails require a
phone-verified YouTube channel.

The new text states the video was published, names the real requirement
(phone-verified channel, youtube.com/verify) and tells the user how to
set this video's thumbnail manually in YouTube Studio.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-10-15 09:26:00 +07:00
Gilad Resisi
454553c4ff fix(instagram): map the rejected comment error 1772107 to a readable message
Meta returns subcode 1772107 ("Instagram Comment Not Added") from the
first comment call after the post itself was published. It fell back to
"Unknown Error", which hid it from the calendar tooltip and suggested
the whole post failed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 09:21:33 +07:00
postiz-contribution[bot]
57a8f1553d
Merge main into staging 2026-10-15 02:08:10 +00:00
Gilad Resisi
6cac1d23f3
Merge pull request #2255 from gitroomhq/fix/posts-valid-crash
fix(frontend): handle a failed /posts/valid response in the post modal
2026-10-15 02:03:16 +00:00
Gilad Resisi
57e1a73c78
Merge pull request #2254 from gitroomhq/fix/invite-cookie-expiry-main
fix(auth): align invite and showorg cookie lifetimes with the token expiry
2026-10-15 02:03:07 +00:00
Gilad Resisi
81292402ed fix(frontend): handle a failed /posts/valid response in the post modal 2026-10-15 08:53:55 +07:00
Gilad Resisi
b958c5d591 fix(auth): align invite and showorg cookie lifetimes with the token expiry
The frontend proxy stored the team-invite token (org cookie) and the
selected-org cookie (showorg) for only 15 minutes. An invitee who opened
the invite link but finished signing up later lost the invite, even
though the link itself is valid for 2 days since #1643, and a member who
joined via the link fell back to the default org after 15 minutes.

Complementary to the invite token expiry extension in #1643: the org
cookie now lives 2 days to match the link, and showorg gets the same
365-day lifetime the backend already uses for it.
2026-10-15 08:36:12 +07:00
postiz-contribution[bot]
18a5ea493e
Merge main into staging 2026-10-14 20:06:44 +00:00
Nevo David
59a50e8bdf Merge remote-tracking branch 'origin/main' 2026-10-14 23:06:27 +03:00
Nevo David
668c971171 feat: delete tool 2026-10-14 23:03:45 +03:00
postiz-contribution[bot]
860ba04f70
Merge main into staging 2026-10-14 11:07:06 +00:00
Gilad Resisi
25916f1274
Merge pull request #2253 from gitroomhq/feat/billing-ai-credits
feat(billing): show the renewal date and remaining AI credits on the billing page
2026-10-14 09:52:46 +00:00
Gilad Resisi
8cfe73a5f6
Merge branch 'main' into feat/billing-ai-credits 2026-10-14 16:44:27 +07:00
Gilad Resisi
5a982c60d6 fix(billing): wait for the stored period too before writing the confirmed plan
On a same-plan Monthly/Yearly switch the stored tier already matches
before the webhook, so the first poll wrote a stale snapshot that
reverted the period toggle and could restore cancelAt. showConfirmedPlan
now waits until both the stored tier and period match the change; the
webhook writes tier, period and cancelAt in one update.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 16:34:18 +07:00
Gilad Resisi
f5963e74c8 fix(billing): refresh the card's totals and credits only once the new plan is stored
The in-place plan change only updates Stripe, the stored plan follows
with the webhook, so refetching the credits right away still returned
the old plan's. The billing cycle card now takes its plan from the
stored subscription and, after a plan change, polls /user/subscription
until it matches, then writes the three credit counts and the
subscription into the cache together. Any failure or a webhook slower
than about 10 seconds leaves the previous values in place.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 16:24:24 +07:00