Skip to content

v1.5.0

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Nov 14:45
18caf80

✨ Features

  • Refreshed the web app, Space and Admin UI to match the Propel design system. UI primitives now come from @makeplane/propel.
  • Added Bulgarian, Georgian and Dutch.
  • Upgraded to React 19, React Router 8, and Tiptap and Hocuspocus v3.
  • The admin and web images now serve with Caddy instead of nginx.
  • Docker images are now built natively for each architecture.

🐞 Bug fixes

  • Fixed external API asset endpoints failing with a server error. Requesting an upload URL for a user or work item asset, and requesting an asset's download URL, returned a 500 on v1.4.3.
  • Fixed work item history returning a server error when requested without an activity type filter.
  • The external API now returns 404 instead of 500 for a work item UUID that doesn't exist, 400 instead of 500 for a JSON body that isn't an object, and 204 instead of 500 when a module's work item is removed twice.
  • Work item attachment uploads now accept size sent as a numeric string.
  • Fixed module state counts in the external API (completed, started, unstarted, backlog and cancelled), which returned 0 or 1 instead of the number of work items.
  • ?expand= now returns null for an empty relation instead of an empty object, and updated_by can be expanded in the app API.
  • Fixed rediss:// Redis URLs losing their credentials and database number.
  • Fixed HTML entities showing in plain-text emails.
  • Fixed Space OAuth callbacks using the wrong host.
  • Snoozed intake items now come back at midnight in the project's timezone.
  • API requests and settings URLs now always use a trailing slash. This fixes requests failing behind some Kubernetes ingresses and the sidebar not highlighting settings pages opened directly.
  • Fixed a reload loop when a session expires.
  • Fixed sub-work items disappearing after they load.
  • Fixed saving profile settings with an empty last name.
  • The editor now honors forced disconnects from the collaboration server.
  • The timeline keeps its scroll position when toggling full screen.
  • Fixed Power K shortcuts for copying a work item's URL and title, and how shortcut keys are shown on Windows and Linux.
  • Pages skip invalid external image sources when collecting their assets.
  • Images whose source URL carries a query string or fragment now resolve to the right asset.
  • The timezone select in profile preferences now stays inside the settings modal with long timezone names.
  • The workspace switcher keeps its actions visible while you scroll the workspace list.
  • Host scripts now use /usr/bin/env bash, so they run on NixOS.
  • The all-in-one image now starts when a host volume is mounted at /app/logs.
  • GUNICORN_WORKERS and AUTHENTICATION_RATE_LIMIT in plane.env now take effect on Docker Compose installs, and swarm.sh accepts its Exit option.
  • Fixed translations in German, Polish, Czech, Korean, Japanese and Russian.

🛡️ Security

This release fixes a large set of access control issues across the app, the external REST API (/api/v1/) and published boards, and hardens sign-in, sessions and deployments. Self-hosted instances should upgrade.

Access control and tenant isolation

  • Refused HTTP verbs that a URL routes to an action its view never defines. Previously PUT on projects, work items and modules fell through to the framework's default handler, which only checked that the caller was signed in, so any account could rewrite those objects and move a project into a workspace it controls.
  • Scoped published board detail routes to the workspace and project in the URL. Previously any signed-in user could read, change or delete another workspace's published boards.
  • Blocked workspace admins from moving a member into another workspace, as an admin, by sending a workspace field when updating the member. Member updates now accept only the role.
  • Limited listing, viewing and deleting project invitations to project admins.
  • Scoped work item comment and relation creation to the project in the URL. Previously a member of one project could comment on or relate a work item in another project or workspace, and the response returned that work item's details.
  • Bound work item, module and cycle IDs in the URL to the URL's project when creating related objects.
  • Required an active Admin or Member role in a draft's project to create, update or convert workspace drafts, and checked the draft's cycle, modules, state, labels, assignees, parent and estimate against that project.
  • Checked page access on every live collaboration connection. Previously only the first connection to load a page was checked, so any signed-in user could join an open page by its ID. Guests now join read-only, and title changes are saved with the editing user's own credentials.
  • Limited project entity search to active members of the project. Previously any workspace member could list another project's members.
  • Required project leads and default assignees to be active workspace members, in the app and the external API.
  • Bound project cover uploads to a project in the URL's workspace that the caller administers.
  • Refused uploads on the legacy per-asset file route, and made the legacy upload endpoint set the project, work item, uploader, size and upload state itself instead of taking them from the request.
  • Required project membership on every workspace-level asset route, including upload, download and duplication, and stopped the external ID lookup from returning asset IDs from other projects.
  • Applied the owning entity's role rules to confirming, updating, deleting and restoring assets: workspace admin for the workspace logo, project admin for the project cover, and project admin or uploader for attachments.
  • Limited export history to the requesting user's own exports.
  • Made work item system fields read-only on update. deleted_at, archived_at, sequence_id and is_draft can no longer be set through PATCH in the app or the external API, so deleting and archiving go through their own permission checks. Ignored fields no longer record activity or send notifications and webhooks.
  • Bound work item history and the comment list, update and delete to a work item in the URL's project. Previously they could be pointed at a work item in another project.
  • Extended the guest restriction to work item attachments, activity, comments, reactions, relations, versions, links and subscribers, and to the attachments, description images and comment images served by asset ID. On a project where guests can't see all work items, a guest previously could read these for work items they didn't create.
  • Applied the same guest restriction to search, work item exports and pages.
  • Required a workspace admin to update a workspace.
  • Limited state changes and project member updates to project admins. Invitation role updates are capped at the updater's own role, and rejoining a public project resets the member's role.
  • Required active project membership for access granted to an object's creator.
  • Required workspace membership to read a global view.
  • Scoped workspace analytics, project stats and grouping, user profile stats and work items, favorites, and activity lookups to projects and objects the caller can see.
  • Scoped project member preferences to the caller.
  • Made notification preference user, workspace and project fields read-only. A user's avatar and cover image now accept only the user's own asset.
  • Blocked mass assignment of protected fields on projects, views and cycles, and bounded pagination cursors and page sizes.

External API

  • Enforced guest_view_all_features on the external API. On a project where guests can't see all work items, a guest can now read only the work items they created, with their comments, links, activity, attachments and relations. The attachment list endpoint now also requires project membership.
  • Stopped trusting created_by and created_at in request bodies for work items, comments and links. Previously a member could re-attribute a work item and then delete it as its creator.
  • Limited editing and deleting comments to the comment's author or a project admin, and deleting attachments to the uploader or a project admin. A project member's role can no longer be set above their workspace role.
  • Brought external API permissions in line with the app: deleting a cycle requires a project admin or the cycle's creator, updating a cycle without owned_by keeps its owner, label writes require a project admin, and adding a project member requires an active workspace membership.
  • Scoped project archive and unarchive to the project in the URL. Previously a member of one project could archive another project.

Published boards

  • Made published board identity fields read-only.
  • Limited public comment edits to the comment's content.
  • Limited changes to public Space assets to their creator, and public uploads to comment attachments.

Authentication and sessions

  • Required a non-empty, matching OAuth state on every OAuth callback in the app and Space.
  • Rejected next_path redirects to other hosts.
  • Required the same origin for cookie-authenticated writes.
  • Marked session, admin session and CSRF cookies Secure whenever WEB_URL is https.
  • Applied sign-in rate limits to every caller by client IP, including instance admin sign-in and sign-up and email-change codes. An email-change code is now invalidated after 5 wrong attempts.
  • Kept the magic code issue limit in place after a code's verification attempts run out.
  • Limited the password length scored for strength, closing a slow-request path on sign-up and password changes.

Content and injection

  • Escaped comment HTML in email notifications.
  • Stripped <style> blocks from emails in linear time.
  • Served assets inline only when the stored file is an allowed image type. Everything else downloads.
  • Checked the export history order_by parameter against an allowlist.

Deployments

  • rediss:// connections now verify the Redis server's certificate and hostname.
  • install.sh, swarm.sh and setup.sh now generate MinIO credentials per install instead of using the template pair.
  • The all-in-one image keeps its generated secrets across restarts and no longer generates a new SECRET_KEY for an existing database.
  • Added an optional NUM_PROXIES setting for the number of proxies in front of the API, used by rate limiting.
  • Updated dependencies and images for current advisories, including Caddy 2.11.7, Django REST framework and certifi (distrusting the emSign roots), minimatch, follow-redirects, qs, fast-uri and OpenTelemetry, and closed the nightly Trivy and Dependabot findings.

⚠️ Upgrade notes

  • Redis over TLS: rediss:// connections now verify the certificate. For a private CA, set REDIS_SSL_CA_CERTS to the CA bundle; to turn verification off, set REDIS_SSL_CERT_REQS=none.
  • Cross-origin writes: browser writes are refused when their Origin is not the instance's own host, a configured base URL, or a CORS or CSRF trusted origin. Requests without an Origin header, such as API clients, are unaffected.
  • MinIO credentials: on upgrade, install.sh and swarm.sh replace the template MinIO credentials with random ones. The API logs a critical warning if MinIO still runs with the template pair.
  • nginx to Caddy: the admin and web images no longer use nginx, so custom nginx config for those images no longer applies.
  • Live collaboration: the live server now checks page access with the API on every connection, so run the live and API images from the same release.
  • PostHog removed: POSTHOG_API_KEY and POSTHOG_HOST are no longer read, and /api/instances/ no longer returns them.
  • External API: created_by and created_at in request bodies are ignored; integrations that set them get the token's user and the current time. Work item sub-resource endpoints (comments, links, activities, attachments, relations) return 404 for a work item that doesn't exist, instead of an empty list.
  • Migrations: three new migrations remove the unused API token is_service and allowed_rate_limit fields, index snoozed intake items, and reset published board identity fields. API rate limits still come from API_KEY_RATE_LIMIT.
  • Source builds: the API's Python dependencies are now managed with uv (apps/api/pyproject.toml and uv.lock) instead of requirements*.txt.