unboundsoftware/pre-commit-node
Archived
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 27 Activity

chore(release): prepare for v0.0.28 #105

Open
group_2759636_bot_9075f203b5d02ced0a8269693de8933b wants to merge 2 commits from next-release into main
pull from: next-release
merge into: unboundsoftware:main
Conversation 0 Commits 2 Files Changed 2
+7 -1
group_2759636_bot_9075f203b5d02ced0a8269693de8933b commented 2025-12-30 16:47:14 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

[0.0.28] - 2025-12-30

⚙️ Miscellaneous Tasks

  • (deps) Update node.js to 482f88d
## [0.0.28] - 2025-12-30 ### ⚙️ Miscellaneous Tasks - *(deps)* Update node.js to 482f88d <!-- generated by git-cliff -->
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
Pull requests that update a dependency file
 docker
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/pre-commit-node#105
Delete Branch "next-release"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?