chore: sync main → dev (merge release history back) #35

Open
john wants to merge 0 commits from main into dev
Owner

Merge main back into dev to sync release merge commits. No code changes — just git history convergence.

Merge main back into dev to sync release merge commits. No code changes — just git history convergence.
Merge pull request 'release: haskytech-seed v0.1.0' (#2) from dev into main
Some checks failed
CI / Detect Changes (push) Successful in 3s
Publish / Publish haskytech-seed (push) Failing after 7s
CI / Lint & Format (push) Successful in 10s
CI / Unit Tests (push) Successful in 13s
62c693186a
Merge pull request 'fix: publish workflow for workspace builds' (#4) from dev into main
Some checks failed
CI / Detect Changes (push) Successful in 3s
CI / Lint & Format (push) Successful in 5s
Publish / Publish haskytech-seed (push) Failing after 9s
CI / Unit Tests (push) Successful in 9s
a6feab5dcb
Merge pull request 'fix: REGISTRY_TOKEN for publish' (#6) from dev into main
All checks were successful
CI / Detect Changes (push) Successful in 3s
CI / Lint & Format (push) Successful in 5s
CI / Unit Tests (push) Successful in 9s
Publish / Publish haskytech-seed (push) Successful in 9s
088d5bec16
Merge pull request 'release: haskytech-haskos-kernel v0.1.0 + forgejo package updates' (#19) from dev into main
Some checks failed
CI / detect-changes (push) Successful in 5s
CI / Lint & Format (push) Failing after 5s
CI / Unit Tests (push) Failing after 6s
81c36366e3
Merge pull request 'release: haskytech-haskos-kernel v0.1.1' (#21) from dev into main
Some checks failed
CI / detect-changes (push) Successful in 4s
Publish / Publish haskytech-forgejo (push) Has been skipped
Publish / Publish haskytech-seed (push) Has been skipped
CI / Unit Tests (push) Failing after 4s
Publish / Publish haskytech-haskos-kernel (push) Successful in 7s
CI / Lint & Format (push) Failing after 5s
3ad7b053b9
feat: add PM entity types to VALID_ENTITY_TYPES (v0.1.2) (#22)
Some checks failed
CI / detect-changes (push) Successful in 5s
CI / Unit Tests (push) Successful in 10s
CI / Lint & Format (push) Successful in 12s
CI / detect-changes (pull_request) Failing after 3s
CI / Lint & Format (pull_request) Has been skipped
CI / Unit Tests (pull_request) Has been skipped
fd0ed8efc6
Some checks failed
CI / detect-changes (push) Successful in 5s
CI / Unit Tests (push) Successful in 10s
CI / Lint & Format (push) Successful in 12s
CI / detect-changes (pull_request) Failing after 3s
CI / Lint & Format (pull_request) Has been skipped
Required
Details
CI / Unit Tests (pull_request) Has been skipped
Required
Details
This pull request has changes conflicting with the target branch.
  • uv.lock
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin main:main
git switch main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
haskytech/haskytech-modules-py!35
No description provided.