build(deps): Bump actions/upload-artifact from 4 to 7 - #125
Merged
adamjohnwright merged 3 commits intoSep 14, 2026
Merged
Conversation
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7
branch
2 times, most recently
from
August 21, 2026 19:33
bcdb193 to
5d02233
Compare
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7
branch
2 times, most recently
from
September 10, 2026 14:00
6ba42d8 to
62bf4bc
Compare
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 7. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v4...v7) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7
branch
from
September 10, 2026 14:47
62bf4bc to
afa6aa2
Compare
adamjohnwright
enabled auto-merge (squash)
September 10, 2026 20:22
adamjohnwright
deleted the
dependabot/github_actions/actions/upload-artifact-7
branch
September 14, 2026 13:46
adamjohnwright
added a commit
that referenced
this pull request
Sep 14, 2026
…nt flag (#202) * feat(deltasignal): the pathway perturbation UI, behind a per-deployment flag Brings #155 onto main. The feature is Chryseisliu's; what is added here is the flag and the update to current main. Taken as content rather than as a merge. The branch was 139 commits behind, and #198 -- which merged main into it and added the flag -- was squashed into it, which flattened main out of its history. The content was then correct and the history was not, so a further merge conflicted in six files for no useful reason. These 23 files are the branch's own diff against main, applied to main. .github/workflows/tests.yml was deliberately left behind: the branch still carries actions/setup-node@v4 and upload-artifact@v4, and taking it would have reverted the two dependabot bumps that landed on main since (#125, #127). The flag: SiteProfile.deltaSignal -> SHOW_DELTASIGNAL -> viewport.showDeltaSignal -> @if around the Perturb button and the panel. Absent means off, so a deployment opts in rather than inheriting a research feature. Only `development` has it on, because /api is routed by proxy.conf.js -- the dev server's proxy, which does not exist in a built artifact and which nothing in deploy.yml or the Apache config provides. Still true, and still the thing between this and a deployed DeltaSignal: the service calls /api/pathways, /api/parse and /api/solve as bare relative paths with no environment indirection, where every other backend here goes through a constant. On a built site those three reach the origin and get index.html back. The flag makes that safe rather than fixed -- the feature is not offered where it cannot work. 210 unit tests, check:types, both ratchets unchanged, and e2e/deltasignal-toggle.spec.ts passes in both states. Co-authored-by: Chryseisliu <Chryseisliu@users.noreply.github.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(deltasignal): default the proxy at the port DeltaSignal is actually on DELTASIGNAL_BACKEND defaulted to http://localhost:8080. On the Reactome dev host 8080 is the Tomcat serving ContentService and AnalysisService, so /api/pathways, /api/parse and /api/solve went there and came back 404 -- a real server denying a real request, which reads as a broken feature rather than an unconfigured one. DeltaSignal's own compose also binds 8080, so the two cannot coexist on this box. It is published on 8090 here; the container still listens on 8080 inside. Verified end to end rather than by reading the config: the backend is up (GET /api/health returns deltasignal-api 0.1.0, Julia 1.10.10), the Angular dev server proxies /api/pathways to it with a 200, and on the development profile the Perturb button renders, the panel opens, and it fetches 200 /api/pathways. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Chryseisliu <Chryseisliu@users.noreply.github.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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.
Bumps actions/upload-artifact from 4 to 7.
Release notes
Sourced from actions/upload-artifact's releases.
... (truncated)
Commits
043fb46Merge pull request #797 from actions/yacaovsnc/update-dependency634250cInclude changes in typespec/ts-http-runtime 0.3.5e454baaReadme: bump all the example versions to v7 (#796)74fad66Update the readme with direct upload details (#795)bbbca2dSupport direct file uploads (#764)589182cUpgrade the module to ESM and bump dependencies (#762)47309c9Merge pull request #754 from actions/Link-/add-proxy-integration-tests02a8460Add proxy integration testb7c566aMerge pull request #745 from actions/upload-artifact-v6-releasee516bc8docs: correct description of Node.js 24 support in README