Skip to content

chore: migrate java-shared-config to monorepo#13481

Open
jinseopkim0 wants to merge 798 commits into
mainfrom
migrate-java-shared-config-v2
Open

chore: migrate java-shared-config to monorepo#13481
jinseopkim0 wants to merge 798 commits into
mainfrom
migrate-java-shared-config-v2

Conversation

@jinseopkim0

@jinseopkim0 jinseopkim0 commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

b/519273974

mpeddada1 and others added 30 commits December 7, 2023 12:08
* fix: move release configs to native-image-shared-config
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* chore(main): release 1.7.1
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
…and pubsub; update junit-vintage to 5.10.2 (#746)

* chore: use sdk-platform-java-config in downstream checks for spanner and pubsub
* fix: update docFX config

* revert version change, handled thru separate PR

* add debugging logs

* add more debugging logs

* remove debugging logs

* remove debug logs
* deps: update actions/github-script action to v7

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
…rtifact (#755)

* chore: merge doclet test with rest of client-library-checks

* add back in separate test

* update script and permissions

* update script

* update permissions

* update permissions

* update permissions

* rename file

* update permissions

* update script

* replace cd with pushd and popd
…rtifact (#759)

* chore: fix storage downstream check to use sdk-platform-java-config artifact
This check is now running in the stage job and is no longer needed in Github.
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* chore: updating contribution guideline

b/323263307

* exclude CONTRIBUTING.md from templates
🤖 I have created a release *beep* *boop*
---


### Updating meta-information for bleeding-edge SNAPSHOT release.

---
This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
…771)

* fix: update DocFX profile with properties

* test: see if these changes are needed
release-please Bot and others added 18 commits June 20, 2025 13:39
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* ci: Test with GraalVM 25

* chore: Fix expected output

* deps: update dependency org.graalvm.sdk:graal-sdk to v25 (#1034)

* deps: update dependency org.graalvm.sdk:nativeimage to v25 (#1035)

---------

Co-authored-by: Mend Renovate <bot@renovateapp.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* test: set up test releaase candidate branches

This repo has a small blast radius for release testing.
We aim to test the rc`n` versioning schema soon to be provided by googleapis/release-please#2622.

Additionally, we test with `prerelease` to understand its behavior.

* chore: use prerelease mode only

Removed prerelease settings and adjusted branch for release.

* chore: use base flags
This property is no longer used upstream. We should only rely on the nativeimage.version property going forward.
* chore: cleanup release-please config

- Remove redundant options already declared at the top level.\n- Remove bumpMinorPreMajor for repositories after the first major release.

* chore: format release-please.yml
Replace old teams with new ones.
b/479542582
#1070)

* ci: sdk-platform-java-config in google-cloud-java in downstream checks

The sdk-platform-java repository has moved to the sdk-platform-java
folder in the google-cloud-java repository. The downstream checks that
use sdk-platform-java-config needs to adjust the location.

* client-library-check-doclet
* fix: Update renovate config check to use npx

* fix: Update renovate config check to use valid version 43.136.0

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request integrates the java-shared-config module (including native-image-shared-config and java-shared-config submodules) into the repository, updating CODEOWNERS, Kokoro, and Cloud Build configurations. It also refactors generation/apply_versions.sh to use a temporary file for sed operations. Key feedback includes correcting a duplicated owner in .github/CODEOWNERS, ensuring mktemp success in the shell script, and removing problematic newlines and whitespace inside XML tags (such as <developerConnection> and dependency exclusions) in the pom.xml files to prevent parsing and SCM command failures.

Comment thread java-shared-config/native-image-shared-config/pom.xml Outdated
Comment thread .github/CODEOWNERS Outdated
Comment thread generation/apply_versions.sh Outdated
Comment thread java-shared-config/java-shared-config/pom.xml
@jinseopkim0 jinseopkim0 changed the title Migrate java shared config v2 chore: migrate java-shared-config to monorepo Jun 15, 2026
@jinseopkim0 jinseopkim0 marked this pull request as ready for review June 15, 2026 21:13
@jinseopkim0 jinseopkim0 requested review from a team as code owners June 15, 2026 21:13
@jinseopkim0 jinseopkim0 requested a review from blakeli0 June 15, 2026 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.