Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
e85c1aa to
cf0b6ad
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2300 +/- ##
==========================================
- Coverage 85.20% 85.19% -0.01%
==========================================
Files 476 476
Lines 10547 10547
Branches 1550 1550
==========================================
- Hits 8987 8986 -1
+ Misses 891 890 -1
- Partials 669 671 +2 🚀 New features to boost your workflow:
|
e49b70a to
75a90e6
Compare
8f6aa96 to
b5d6f01
Compare
| timeout-minutes: 60 | ||
| steps: | ||
| - name: Validate access to version data service | ||
| uses: embrace-io/public-actions/upload-sdk-version@88167cd1a3fce3418e26c8c842026e6dfab99e41 |
There was a problem hiding this comment.
It is ok to pin things to this SHA?
There was a problem hiding this comment.
That's how it's done everywhere, at least for this particular action. I'm not a fan, but I think it's the only way to make an action immutable. @fnewberg might have additional reasons
There was a problem hiding this comment.
Feels like "current version" should be defined as a variable and be referenced everywhere so we don't have to make N changes when the version revs. Not a blocker - just something to consider.
|
|
||
| on: | ||
| schedule: | ||
| - cron: '0 16 * * *' # Runs every day at 16:00 UTC |
There was a problem hiding this comment.
This is in the middle of a work day. Why not 5 UTC or something to ensure it's done when Jamie gets online?
| - name: Setup Java | ||
| uses: actions/setup-java@v4 | ||
| with: | ||
| distribution: 'adopt' |
There was a problem hiding this comment.
Is there a way we can apply the same Java config to all of our builds, production, snapshot, and otherwise?
There was a problem hiding this comment.
we could use a shared workflow, though I'm not sure if it'd work
bidetofevil
left a comment
There was a problem hiding this comment.
LGTM. Some comments about logic consolidation and snapshot timing but not blocking
b5d6f01 to
ab1aac5
Compare
* Migrate to vanniktech maven publish (#2300) * Update publish-api-docs.yml to handle hotfixes * Update upload-artifacts-to-maven-central.yml to accept hotfixes
Goal
Use https://github.com/vanniktech/gradle-maven-publish-plugin for publishing to Maven Central. We were using a temporal workaround, and this plugin seems better maintained and widely used in many other projects.
Changes:
I released two test versions, one without changes, one with the vanniktech plugin. They both look the same, same artifacts are uploaded, and they both work when tested manually.