Skip to content

feat: Sync master with Latest Changes#63

Merged
meetKazuki merged 53 commits into
masterfrom
develop
May 18, 2026
Merged

feat: Sync master with Latest Changes#63
meetKazuki merged 53 commits into
masterfrom
develop

Conversation

@meetKazuki

Copy link
Copy Markdown
Owner

What does this PR do?

Description of Task to be completed?

How should this manually be Tested?

What are the relevant Planner stories?

Screenshots (if appropriate)

* ci: move to ghcr

* chore: update Dockerfile
* feat: improve editor (#2)

* chore: containerize application (#3)

* chore: add CI pipeline, release workflow (#4)

* chore: add status badges to README.md (#5)

* refactor: refactor release process (#7)

* test: add tests for @homelab-stackdoc/core package (#8)

* ci: Move to `GHCR` (#9)

* ci: move to ghcr

* chore: update Dockerfile
* feat: redesign/re-implement nodes and layout

* feat: improve edge routing

* feat: improve group outline clipping

* feat: polish adjacent group spacing

* chore: adjust split ratio

* fix: fix failing tests
* feat: add port connections view

* chore: standardize code style
* chore: resolve merge conflicts

* chore: update sample.yaml
* chore: set up api project

* chore: set up api project

* chore: set up api project

* fix: gitguardian unecessary warning

* chore: add notes for dev environment deployment

* chore: add global prefix to api app setup
* chore: cleanup project configuration

* chore: remove tsbuildinfo.json
* feat: add template and gallery components

* chore: update class names
meetKazuki and others added 22 commits May 13, 2026 22:22
* feat(core): add subgroups

* feat(core): add subgroups
chore: Sync `master` to `develop`
* feat: improve visuals across editor, configs, gallery & template (#52)

* feat: improve editor (#2)

* chore: containerize application (#3)

* chore: add CI pipeline, release workflow (#4)

* chore: add status badges to README.md (#5)

* refactor: refactor release process (#7)

* test: add tests for @homelab-stackdoc/core package (#8)

* ci: Move to `GHCR` (#9)

* ci: move to ghcr

* chore: update Dockerfile

* docs: update documentation for branching and coolify ghcr deployment (#12)

* chore: Sync `develop` to `master` (#11) (#13)

* feat: improve editor (#2)

* chore: containerize application (#3)

* chore: add CI pipeline, release workflow (#4)

* chore: add status badges to README.md (#5)

* refactor: refactor release process (#7)

* test: add tests for @homelab-stackdoc/core package (#8)

* ci: Move to `GHCR` (#9)

* ci: move to ghcr

* chore: update Dockerfile

* chore: update release-please with target branch (#16)

* feat: Improve Visual Layout (#18)

* feat: redesign/re-implement nodes and layout

* feat: improve edge routing

* feat: improve group outline clipping

* feat: polish adjacent group spacing

* chore: adjust split ratio

* fix: fix failing tests

* feat: add service icons from selfh.st/icons (#19)

* feat: add port connections (#20)

* feat: add port connections view

* chore: standardize code style

* feat: polish ui (#23)

* chore: Resolve Merge Conflicts (#25)

* chore: resolve merge conflicts

* chore: update sample.yaml

* chore: Set Up API (#28)

* chore: set up api project

* chore: set up api project

* chore: set up api project

* fix: gitguardian unecessary warning

* chore: add notes for dev environment deployment

* chore: add global prefix to api app setup

* fix: fix typecheck (#29)

* chore: split builder into separate stages (#30)

* fix: fix missing files in docker build (#31)

* fix: fix api routing (#32)

* fix: fix api routing (#33)

* chore: cleanup project configuration

* chore: cleanup project configuration

* chore: remove tsbuildinfo.json

* fix(ci): typecheck depends on packages build; fix api healthcheck path (#35)

* feat(web): implement config sharing feature (#36)

* feat: github oauth (#37)

* feat: template and gallery components

* feat: add template and gallery components

* chore: update class names

* feat(web): add page-level chrome strip to editor and shared view (#39)

* feat(core): add subgroups (#40)

* feat(core): add subgroups

* feat(core): add subgroups

* feat(core,renderer): improve labelled ports (#41)

* feat(core): parallel links (#42)

* feat(renderer): 2d density (#43)

* chore(packages): source code audit (#44)

* feat(renderer): improve detail modal (#48)

* feat: improve templates visuals (#49)

* feat: improve share panel (#50)

* feat: empty/error/loading states across editor & shared view (#51)

* chore: release 0.4.0 (#53)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* feat: add landing page

* chore: remove uneccessary comments
* chore: add seeder script for templates

* update: update templates
@gitguardian

gitguardian Bot commented May 18, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
30219896 Triggered Generic Password e83171f compose.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@meetKazuki meetKazuki merged commit b012923 into master May 18, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant