Upgrade dependencies #210
Merged
Upgrade dependencies #210
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Move from 'release candidate' to proper beta releasing. Update README accordingly. Release as 17.3.0-beta-1.
Removed customDeps as we don't support scala 2.11 any more
5 tasks
rowannekabalan
approved these changes
Feb 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Upgrade our dependencies and plugins to their latest available versions. This build brings in beta releases of some upstream libraries for testing while they have their own PRs open.
This branch was used to release the following builds;
content-api-models-json 17.3.0-beta.2 for scala 2.12
content-api-models-json 17.3.0-beta.2 for scala 2.13
content-api-models 17.3.0-beta.2
and
@guardian/content-api-models 17.3.0-beta.2 for typescript
(note that the maven links above may take some time to appear)
How to test
Testing the NPM build for vulnerabilities;
How can we measure success?
Consumers build and test cleanly? Success!
Have we considered potential risks?
Risks should be minimal - it will require a specific action to incorporate this library into an application so nothing should inadvertently break (and we believe it's still fully functional anyway)
Images
N/A
Accessibility