6 Commits

Include renames

Author	SHA1	Message	Date
Liosha84	9d03b0977d	fix(ci): split drone into two separate pipelines for PR and main	2026-10-29 00:55:51 +01:00
Liosha84	eb73c55ac2	fix(drone): use full commit SHA for Docker tag and fix non-interactive adduser ... - Replace bash substring syntax ${DRONE_COMMIT_SHA:0:7} with ${DRONE_COMMIT_SHA} which is supported by Drone YAML variables - Use 'adduser -D -g ""' in Dockerfile to skip interactive prompts for user information during Docker image build	2026-10-29 00:47:28 +01:00
Liosha84	d4a6726930	feat: automatic releases on merge to main ... - Drone now triggers on push to main branch instead of Git tags - Each merge produces two Docker tags: main-{commit-sha} and main-latest - No manual Git tags needed — merging PR develop → main is the release - Updated docs/DEVELOPMENT.md with new Git-flow workflow - Updated CHANGELOG.md with automatic releases feature	2026-10-29 00:39:31 +01:00
Liosha84andJunie	291167e683	feat(drone): add pull request trigger for CI/CD testing ... Co-authored-by: Junie <junie@jetbrains.com>	2026-10-29 00:19:31 +01:00
Liosha84andJunie	7f2ea4f3b4	Fix Drone CI/CD: use from_secret instead of from for secrets ... The correct Drone syntax for referencing secrets is 'from_secret:', not 'from:'. Without this fix, Drone cannot read the registry credentials and the docker login step will fail with 401 Unauthorized. Co-authored-by: Junie <junie@jetbrains.com>	2026-10-29 00:00:17 +01:00
Liosha84andJunie	923b1e7c57	Migrate CI/CD from Gitea Actions to Drone ... Replace .gitea/workflows/docker.yml with .drone.yml using the Drone Docker plugin with auto_tag enabled. On Git tag pushes (v0.2.0), Drone automatically creates Docker image tags: full version (0.2.0), minor version (0.2), and latest. Updated docs/DEVELOPMENT.md to document Drone CI/CD setup instead of Gitea Actions. Updated CHANGELOG.md to reflect the Drone migration. Co-authored-by: Junie <junie@jetbrains.com>	2026-10-28 23:57:30 +01:00