chore: sync main into the monorepo-conversion branch (post-#37 changes)#39
Merged
kamal-kaur04 merged 2 commits intoJul 10, 2026
Conversation
Pin returntocorp/semgrep container image to a specific version and GitHub Actions to major version tags to prevent :latest tag resolution and reduce supply-chain attack surface. Fixes: LCNC-15821 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
kamal-kaur04
approved these changes
Jul 10, 2026
62223e6
into
migration/monorepo-add-wdio-browserstack-service
3 checks passed
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.
What
Brings the PR #37 branch (
migration/monorepo-add-wdio-browserstack-service) up to date withmain. Only one commit had landed onmainsince #37 was opened:f1c3688— semgrep workflow: pin Docker image (returntocorp/semgrep:1.166.0) and actions to version tags (a security hardening).No release/version-bump commits were outstanding — everything else on
mainwas already in the PR branch. The merge auto-resolved cleanly (the only touched file,.github/workflows/Semgrep.yml, merged without conflict; the version pin is applied on top of the branch's Semgrep config).Why base = the PR #37 branch
Merging this into
migration/…keeps PR #37 current withmainbefore it merges, so the eventualmainmerge is a clean fast-forward with no drift.🤖 Generated with Claude Code