Skip to content

Commit

Permalink
chore: release main
Browse files Browse the repository at this point in the history
  • Loading branch information
release-please[bot] authored Nov 26, 2024
1 parent 53ab7ec commit 7fb5d48
Show file tree
Hide file tree
Showing 4 changed files with 11 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"packages/cron-utils": "5.0.0",
"packages/datastore-lock": "6.0.0",
"packages/flakybot": "1.2.2",
"packages/gcf-utils": "16.2.0",
"packages/gcf-utils": "16.2.1",
"packages/git-file-utils": "2.0.0",
"packages/issue-utils": "4.0.0",
"packages/label-utils": "5.0.0",
Expand Down
7 changes: 7 additions & 0 deletions packages/gcf-utils/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,13 @@ See [Conventional Commits](https://conventionalcommits.org) for commit guideline



## [16.2.1](https://github.com/googleapis/repo-automation-bots/compare/gcf-utils-v16.2.0...gcf-utils-v16.2.1) (2024-11-26)


### Bug Fixes

* set default taskTargetName based on runtime environment ([#5585](https://github.com/googleapis/repo-automation-bots/issues/5585)) ([53ab7ec](https://github.com/googleapis/repo-automation-bots/commit/53ab7ecb05492b8f3cf46f0a77fbd88727dfffb0))

## [16.2.0](https://github.com/googleapis/repo-automation-bots/compare/gcf-utils-v16.1.1...gcf-utils-v16.2.0) (2024-11-25)


Expand Down
4 changes: 2 additions & 2 deletions packages/gcf-utils/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion packages/gcf-utils/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "gcf-utils",
"version": "16.2.0",
"version": "16.2.1",
"description": "An extension for running Probot in Google Cloud Functions",
"scripts": {
"compile": "tsc -p .",
Expand Down

0 comments on commit 7fb5d48

Please sign in to comment.