Update examples with Nutrient SDK version 1.22.0 - #108
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Update examples with Nutrient SDK version 1.22.0#108github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
This file contains hidden or 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
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.
Automated bump of
@nutrient-sdk/viewerfrom 1.21.0 to 1.22.0.Verification
Checks ran inside the workflow before this pull request was opened. A
pull request created by
GITHUB_TOKENdoes not trigger the Biome orPlaywright workflows, so the checks tab here will be empty.
in
pnpm-workspace.yamland the corresponding lockfile updatespnpm run format): applied toexamples/pnpm run e2e-tests): ❌ failed. The failing examples are named at the end of the run log.Workflow run
This draft needs a human
The e2e suite failed, so this was opened as a draft and GitHub did not
request code owners on it. It will not retry on its own: every future
scheduled run sees this pull request and skips 1.22.0. Re-running
the workflow for 1.22.0 will not help either, for the same reason.
Pick one:
reopen it. Reopening it yourself fires
pull_request: reopened,which the Biome and Playwright workflows act on, so they run against
this bump and report in the checks tab. Marking a draft ready for
review triggers nothing, so it is not a substitute.
update-examples-1.22.0. A push fromyour own account runs those same checks. Then mark this ready for
review.
the branch in place. 1.22.0 will not be proposed again.