chore(e2e): bump e2e-test-utils to 2.1.8 for bulk-import - #3240
chore(e2e): bump e2e-test-utils to 2.1.8 for bulk-import#3240gustavolira wants to merge 1 commit into
Conversation
|
🤖 Finished Review · ✅ Success · Started 8:42 PM UTC · Completed 8:46 PM UTC Commit: |
Review — approveScope: Patch-level dev dependency bump ( SummaryThis PR bumps the Analysis
No findings. Labels: Patch-level dev dependency bump in bulk-import e2e tests Previous runReview — approveScope: SummaryPatch-level bump of CorrectnessThe ConsistencyFour other workspaces ( SecurityDev dependency only, used exclusively for E2E test execution. No production artifact impact. ScopeChanges are correctly limited to a single workspace ( No findings. Previous run (2)Looks good to me Previous run (3)Review — approveScope: SummaryPatch-level bump of Analysis
No findings. Labels: Bumps a devDependency in an existing workspace e2e-tests directory Previous run (4)ReviewVerdict: Approve — clean dependency version bump with no findings. SummaryBumps Dimensions reviewed
Labels: E2E dev-dependency version bump in an existing workspace Previous run (5)Review — approvePR: SummaryPatch-level version bump of Analysis
Version risk assessmentThis is a patch-level bump within the same minor series (2.1.x). No major version boundary crossed, so no breaking API changes are expected. The 2.1.8 release carries the coverage collection fix already validated by three other workspaces in merged PRs (#3200, #3235, #3201). No findings. Labels: Dependency version bump in E2E test workspace |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
ready-for-merge
9c7de5e to
8bfcbb3
Compare
|
🤖 Finished Review · ✅ Success · Started 10:38 PM UTC · Completed 10:44 PM UTC Commit: |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
ready-for-merge
8bfcbb3 to
07dfa69
Compare
|
🤖 Finished Review · ✅ Success · Started 10:59 PM UTC · Completed 11:03 PM UTC Commit: |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
ready-for-merge
|
/publish |
|
Publish workflow has completed with success. Publishing process✅ Finished successfully. ✅ Published container images:
Backstage Compatibility Check✅ All workspaces are compatible with the target Backstage version ( No action required. Metadata Validation✅ All metadata files validated successfully. Running e2e tests |
|
✅ Smoke tests workflow passed. All plugins loaded successfully. |
❌ Failed E2E Tests -
|
github-actions
Bot
added
the
mandatory-workspace
07dfa69 to
eaf36ff
Compare
|
🤖 Review · ❌ Terminated · Started 12:41 PM UTC · Ended 12:47 PM UTC Commit: |
|
/publish |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
ready-for-merge
|
🤖 Finished Review · ✅ Success · Started 12:41 PM UTC · Completed 12:47 PM UTC Commit: |
|
Publish workflow has completed with success. Publishing process✅ Finished successfully. ✅ Published container images:
Backstage Compatibility Check✅ All workspaces are compatible with the target Backstage version ( No action required. Metadata Validation✅ All metadata files validated successfully. Running e2e tests |
|
✅ Smoke tests workflow passed. All plugins loaded successfully. |
❌ Failed E2E Tests -
|
|
/test e2e-ocp-helm |
❌ Failed E2E Tests -
|
eaf36ff to
374ecda
Compare
|
🤖 Finished Review · ✅ Success · Started 8:50 PM UTC · Completed 8:53 PM UTC Commit: |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
ready-for-merge
bulk-import is still on 2.1.6. 2.1.8 carries the coverage collection fix that intelligent-assistant (redhat-developer#3200), adoption-insights (redhat-developer#3235) and the workspaces in redhat-developer#3199 already picked up. One workspace per PR: the Prow e2e step refuses to run when more than one workspace changed, so a combined PR produces no coverage at all. Lockfile regenerated with yarn 4.17.1 using --mode=update-lockfile.
374ecda to
5a9a62a
Compare
|
|
🤖 Finished Review · ✅ Success · Started 5:28 PM UTC · Completed 5:31 PM UTC Commit: |
fullsend-ai-review
Bot
added
ready-for-merge
|
/publish |
1 similar comment
|
/publish |
|
Publish workflow has completed with success. Publishing process✅ Finished successfully. ✅ Published container images:
Backstage Compatibility Check✅ All workspaces are compatible with the target Backstage version ( No action required. Metadata Validation✅ All metadata files validated successfully. Running e2e tests |
|
Publish workflow has completed with success. Publishing process✅ Finished successfully. ✅ Published container images:
Backstage Compatibility Check✅ All workspaces are compatible with the target Backstage version ( No action required. Metadata Validation✅ All metadata files validated successfully. Running e2e tests |
|
✅ Smoke tests workflow passed. All plugins loaded successfully. |
❌ Failed E2E Tests -
|
|
@gustavolira: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
2 participants
bulk-importis still on@red-hat-developer-hub/e2e-test-utils2.1.6. 2.1.8 carries the coverage collection fix thatintelligent-assistant(#3200),adoption-insights(#3235),tech-radar(#3201) and the workspaces in #3199 already picked up.Lockfile regenerated with yarn 4.17.1 (the pinned
packageManager) using--mode=update-lockfile, so only the resolution and checksum move.One workspace per PR
The Prow e2e step refuses to run when more than one workspace changed:
A combined PR therefore produces no coverage at all — which is why #3199, touching three workspaces, never ran e2e, and why this arrives as one PR per workspace rather than one for the set.
Why now
bulk-importis lined up for the upstream per-file coverage path (#3231, #3238), which consumes a Prow run's raw coverage JSONs. Those only exist while the run's artifacts are retained, so publishing a workspace needs a recent green e2e for it. The bump is worth doing on its own; it also produces the run.Published so far through that path:
intelligent-assistant(99 files) andadoption-insights(39 files), both browsable per file on the rhdh-plugins Codecov project.After merge
Nothing further is needed here. The coverage publish is a separate
workflow_dispatch(publish-coverage-upstream.yaml) pointed at the run's artifacts.🤖 Generated with Claude Code