Skip to content

fix: bypass secrets check in CI#23

Merged
dkhawk merged 2 commits intomainfrom
fix/gradle-secrets-enforcement-breaking-tests
Jan 27, 2026
Merged

fix: bypass secrets check in CI#23
dkhawk merged 2 commits intomainfrom
fix/gradle-secrets-enforcement-breaking-tests

Conversation

@dkhawk
Copy link
Collaborator

@dkhawk dkhawk commented Jan 27, 2026

Bypasses the secrets.properties check when running in CI environments to prevent build failures. Also fixes the package name in the launchDebug task.

@dkhawk dkhawk requested a review from kikoso January 27, 2026 00:38
@@ -0,0 +1,3 @@
{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove this file, and add instead a .vscode line to the .gitignore?

Copy link
Collaborator

@kikoso kikoso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a comment regarding the vscode folder.

@dkhawk dkhawk merged commit 7c466f6 into main Jan 27, 2026
7 checks passed
@dkhawk dkhawk deleted the fix/gradle-secrets-enforcement-breaking-tests branch January 27, 2026 15:55
googlemaps-bot pushed a commit that referenced this pull request Jan 27, 2026
# [1.4.0](v1.3.0...v1.4.0) (2026-01-27)

### Bug Fixes

* bypass secrets check in CI ([#23](#23)) ([7c466f6](7c466f6))
* Relax secrets.properties enforcement for CI and Release builds ([#24](#24)) ([8b64d1e](8b64d1e))

### Features

* Add secrets plugin check to ApiDemos and Advanced samples ([#22](#22)) ([45bae7a](45bae7a))
@googlemaps-bot
Copy link

🎉 This PR is included in version 1.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants