Repository navigation
Releases
v2.1.0
This release makes live updates dependable in the first second after a page opens, puts the chat on the connection the board already holds, and trims a few requests and queries. Nothing breaks API clients.
Features
Chat and live updates
- A chat message sent right after opening the panel is shown at once; before, it was stored but did not appear until the panel was reopened
- The chat panel shows your own join notice, and catches up on anything said while it was connecting
- A board change made just after a page load or a reconnect is no longer missed: the board reads itself once more when its live connection is confirmed
- The send button stays disabled until the chat can actually receive the answer
Architecture
- One socket per page. The board and the chat share a single connection, so opening the chat panel costs no second socket, sign-in or broker session
- A subscription counts as live only when the broker confirms it. RabbitMQ takes up to a second to open one and drops what is published before then, so the client acts on the broker's receipt and not on having asked
- Fewer requests and queries. No avatar is requested for a board member who has none, a card's next move is numbered with one query, a board's task deletes go out in batches, and the fonts are served from the hashed bundle with long-lived caching
- The API image is layered. Dependencies, the loader and the application code sit in separate layers, so a code change pulls only the last one
- The chat is covered end to end. A Cypress spec sends board and direct messages between two accounts on the running stack
Operations
- CI: a new push to a pull request cancels its superseded runs in six more workflows
- Local stack: Grafana gets the memory version 13.3.1 needs to start
Images
ghcr.io/dominiksmolinski3/kanbanproject-app:2.1.0
ghcr.io/dominiksmolinski3/kanbanproject-web:2.1.0
ghcr.io/dominiksmolinski3/kanbanproject-grafana:2.1.0
All three carry the same tag and must be deployed together.
Full history: 11 commits since v2.0.0.
v2.0.0
This release is mostly security and correctness work on sign-in, chat and boards, found by reading the code and then testing a running stack, plus a round of query and payload reductions. Four changes break API clients, which is why it is a major version; the bundled web and Android clients already send what the API now expects.
Breaking changes
- Column and row lists no longer carry their tasks.
GET /api/columnsandGET /api/rowsanswerid,name,positionandwipLimitonly. Read tasks from the task endpoints - Deleting an account needs the current password.
DELETE /api/users/{id}takes a body withcurrentPassword; without it the answer is a 400 - Verifying a signup needs the password.
POST /api/auth/verifytakespassword, the one chosen at signup, besideemailandverificationCode - Deadlines are instants. A task's deadline, and the search's
deadlineFromanddeadlineTo, are ISO-8601 with an offset (2026-12-01T16:00:00Z); a time without one is a 400. Stored deadlines were converted as Europe/Warsaw times
Features
Boards
- People are told at once when a board they can see is renamed, deleted, shared or handed over, and a member who is removed leaves the board with a notice instead of an error on the next click
- Invitations expire after 14 days, and one account can send at most 20 invitation mails a day
- Deleting a row warns when some of its cards could not be moved first
- Columns and rows can be renamed without a mouse, and every control has a name for a screen reader
Accounts and sign-in
- The shared demo accounts can no longer have their password, address or account taken or deleted
- A signup for an address that is still unverified replaces the earlier one, so whoever registered an address first cannot keep a password on it
- Verification and email-change codes are stored hashed, wrong guesses are counted even when sent at the same moment, and the account locks after too many
- Withdrawing every session now also ends issued access tokens and open sockets
- Signup, resend and password reset take the same time whether or not the address has an account
- A password longer than 72 bytes is refused as a validation error instead of a server error
- A session survives a failed sign-in check or an expired access token, and is renewed once across tabs
Chat
- Direct messages reach a person whose socket is on another API replica
- A client may send only to
/appand subscribe only to the destinations it is entitled to; the token is checked on every frame, and a board's frames stop for someone who lost the board - Sending is limited to five frames a second per account, with a burst of twenty
- An account's conversations follow it when its email address changes
Fixes you may notice
- A board with two or more tasks can be deleted again
- A card turns overdue at the same moment for everyone, whatever their time zone
- A per-person WIP limit counts only open assignments
- An account that owns or shares boards can be deleted; its boards pass to another member or go with it
- Invitation mail cannot be made to carry a link written by the inviter
Architecture
- Times are instants throughout the API and the database (
timestamptz), not zone-less wall-clock values - Board changes are events.
BoardServicepublishes who a change touches, and each of them gets a notice on a queue of their own after the commit - Fewer and smaller reads. Board roles for a list come in one query, open assignments are counted in the database, an access token is parsed once per check, deadlines have a partial index, and a board's chat, activity, history and invitations are deleted in one statement each
- File transfers hold no database connection. Attachments and avatars are streamed outside a transaction, and a blob is removed if its row cannot be written
- The edge compresses the bundle and the proxied JSON
- The metrics endpoint is no longer served over HTTP, and logs name accounts by id, not by email address
- Tests against a real Postgres cover what a mocked suite cannot answer: foreign keys, locks and transaction boundaries. Every package has a coverage floor just under what it measures
Operations
- CI: every job has a timeout, path-filtered workflows end in a gate the ruleset can require, workflows and shell scripts are linted, pull requests are checked against the commit and labelling conventions, and a pull request that edits a merged migration is refused
- Security scanning: CodeQL runs the extended queries and analyses Python, the dependency sweep fails on a high or critical finding and covers the images Terraform pins and the binaries the monitoring VM installs, the API is scanned signed in, and the repository is scored by OpenSSF Scorecard
- Releases: only a tested commit whose images CD signed can be released
- Monitoring: Grafana 13.3.1, Prometheus, blackbox_exporter and node_exporter from hardened rebuilds, and a hung Postgres or Redis shows as down
- Android: Android Gradle Plugin 9.5 and Gradle 9.8
- Routine dependency bumps across Maven, npm, Docker images, Terraform providers and actions
Images
ghcr.io/dominiksmolinski3/kanbanproject-app:2.0.0
ghcr.io/dominiksmolinski3/kanbanproject-web:2.0.0
ghcr.io/dominiksmolinski3/kanbanproject-grafana:2.0.0
All three carry the same tag and must be deployed together.
Full history: 163 commits since v1.1.0.
v1.1.0
The frontend is now TypeScript from the services layer to the entry points, server reads go through TanStack Query, and there is an Android app. The API and the database are unchanged (no backend source, no migrations), and nothing here is a breaking change.
Features
Android app
- The web app, wrapped with Capacitor and bundled into a native shell that calls a deployed API. It is Android only and a debug build for now; a signed release build, push notifications and iOS are not done
- The API origin is set at build time (
VITE_API_ORIGIN), and a mobile build without one is refused. The deployment the app talks to must listhttps://localhostinSECURITY_CORS_ALLOWED_ORIGINS - Android backup is off, because both tokens live in the app's local storage
Fixes
- Time spent in a column, in a task's history, is now formatted in the reader's own language
Behavior you may notice
- Opening a page, a task panel or a search shows what it last read at once and refreshes behind it, instead of starting empty
- Switching boards no longer leaves the previous board on screen while the new one loads
- An error that was shown after a failed read goes away when a later read succeeds, instead of staying until a reload
- A task that has no row is put in the first row on every read, not only the first
- Opening the search panel runs its first search at once rather than after the typing delay
Architecture
- TypeScript across the app: services, contexts, hooks, components and entry points, checked by
tscin CI. The services layer goes through a few typed request helpers, and the guard tests that read the sources were extended to read them - TanStack Query for the server reads a screen shows, except the two that are edit forms (the task panel's fields and a subtask's description). Board data, boards and invitations, the task panel, users, search, activity, devices and flow metrics are queries; the cache is per session and is emptied on sign-out, and live sync invalidates it instead of dispatching window events
- Radix UI for dialogs: one modal primitive under the form, confirm and task-panel dialogs, with a focus trap, a name and scroll locking
- React Hook Form on the sign-in screen
- The largest components were split into small hooks and components, and shared pieces replace code that was written two or three times (outside-click handling, form tabs, the pending and error state of forms)
Operations
- CI now builds the Android debug APK when the Android project or its dependencies change, and type-checks the frontend on every PR
- Pushing a
vX.Y.Ztag now gives the three images of that commit their version tag, after checking that the tag, the three version files andmainagree - Dependabot watches the Android Gradle project and moves the
@capacitorpackages together - A transitive
uuidwith a published advisory is overridden to a fixed version - Terraform: an
azurermprovider bump and no resource changes - Routine dependency bumps: Azure SDK BOM, azurerm, the Node image, the React and minor-and-patch npm groups, and the actions group
Images
ghcr.io/dominiksmolinski3/kanbanproject-app:1.1.0
ghcr.io/dominiksmolinski3/kanbanproject-web:1.1.0
ghcr.io/dominiksmolinski3/kanbanproject-grafana:1.1.0
All three carry the same tag and must be deployed together.
Full history: 55 commits since v1.0.0.
v1.0.0
The first tagged release of KanbanProject: a multi-user Kanban board where teams share boards, move cards in real time and see how work flows. It has a Spring Boot API, a React SPA, and the full Azure infrastructure to run it, defined as Terraform.
Features
Boards and access
- Boards with members in three roles: owner (rename, delete, manage members), member (edit everything on the board) and viewer (read-only, enforced by the API on every write)
- Invitations by email, which the invitee accepts or declines
- Other tenants' boards are invisible: a board you are not on answers 404, not 403
Working on the board
- Columns and rows (swimlanes) with drag-and-drop; every drag also works from the keyboard
- Tasks with subtasks, labels, assignees, deadlines and file attachments (streamed to and from Azure Blob Storage)
- Comments on tasks, and a per-task history of every move
- WIP limits on columns, rows and users; per-user limits are enforced by the API
- Task search across a board
- Edit conflicts are detected instead of silently overwritten (optimistic locking)
Live collaboration
- Live board sync: changes from other users and other tabs show up immediately, across every API replica (STOMP over RabbitMQ)
- Chat for each board, with message history
- Activity feed of who moved, assigned, completed or commented on what
Insight
- Flow metrics built from every card's move history: cumulative flow, cycle time and throughput
Accounts
- Sign-up with an emailed verification code, password reset, optional Google reCAPTCHA on login
- Short-lived JWT access tokens with refresh tokens stored as hashes; a list of signed-in devices where any one can be signed out
- Email reminders for overdue tasks, in the recipient's own language
- User avatars
Interface
- Nine languages: English, Polish, German, Spanish, French, Italian, Russian, Japanese and Arabic (with a right-to-left layout)
- Dark mode that follows the operating system
- The "Noren" redesign
Architecture
- API: Spring Boot 4.1 (Java 21, built and run on JDK 25), organised as one package per feature, with an OpenAPI contract at
/v3/api-docs - Web: React 19 + Vite 8, served by nginx. nginx is the only public address and reverse-proxies
/api,/wsand/v3/api-docsto the API - State: PostgreSQL with Flyway migrations, Azure Managed Redis (shared rate-limiter state), RabbitMQ (STOMP relay), Azure Blob Storage (attachments and avatars) and Azure Communication Services (email)
- All shared state lives outside the API, so both
webandapirun with more than one replica
Operations
- Infrastructure as code: Terraform for Azure Container Apps (web, api, broker, Grafana), PostgreSQL Flexible Server, Redis, Key Vault and Storage, all reached over private endpoints with managed identities and no account keys
- Jobs: Flyway migrations, a nightly
pg_dumpto a second region and a nightly restore drill - CI/CD: backend and frontend tests, Cypress end-to-end tests against a two-replica stack, and a Trivy scan of every image on every PR; CD builds, scans and publishes the images
- Security: CodeQL, dependency review and scanning, DAST, an external attack-surface scan, Hadolint, Checkov, and a strict Content-Security-Policy
- Drift detection: nightly Terraform plans, monitoring-VM drift checks and a daily check of the deployed contract
- Observability: Prometheus and Grafana with dashboards for the API, JVM and connection pool, the app's own counters, the infrastructure and the edge, plus Application Insights
- Load testing: k6 scenarios in
loadtest/
Images
ghcr.io/dominiksmolinski3/kanbanproject-app:1.0.0
ghcr.io/dominiksmolinski3/kanbanproject-web:1.0.0
ghcr.io/dominiksmolinski3/kanbanproject-grafana:1.0.0
All three carry the same tag and must be deployed together. To run the full stack locally, see Using Docker in the README.
Full history: 1,200+ commits since March 2025.