2009 Commits
Author SHA1 Message Date
mvdbeek aa0f6246b8 Merge branch 'release_26.2' into dev 2026-11-19 06:09:44 +01:00
Nicola SoranzoandClaude Opus 5.5 3f1a74d25a Recommend Python 3.12 or 3.13 for Galaxy 26.2
Address review comments on
https://github.com/galaxyproject/galaxy/pull/24907 :

- Move the release note about the removal of Python 3.10 support from
  "Deprecation Notices" to "Admin Notes", as done for Python 3.8 in
  `25.0_announce.rst`.
- Mention that the requirement also applies to the Python used on compute
  nodes to run job-side code when Galaxy's virtualenv is not shared.
- Recommend Python 3.12 or 3.13, since Python 3.11 reaches its
  end-of-life in October 2027, within the support period of Galaxy 26.2
  (see
  https://github.com/galaxyproject/galaxy/pull/24907#discussion_r4584251159
  ). TensorFlow, used for tool recommendations, doesn't support Python
  3.14 yet.
- Raise the default `GALAXY_CONDA_PYTHON_VERSION` in
  `scripts/common_startup.sh` from 3.11 to 3.13 accordingly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 21:57:55 +00:00
Nicola SoranzoandClaude Opus 5.5 1d47298149 Update tensorflow conditional dependency to 2.21.0
`tensorflow` 2.15.1 only supports Python up to 3.11, while 2.21.0 (the
latest release) supports Python 3.10 to 3.13. It also resolves against
Galaxy's pinned requirements apart from `h5py` (it needs `h5py<3.15.0`),
whereas 2.15.1 requires `numpy<2` and `wrapt<1.15`.

To keep `tensorflow` from downgrading the pinned `h5py` on every startup,
add `lib/galaxy/dependencies/conditional-overrides.txt`, which drops the
`h5py` upper bound, and pass it with `--override` to the conditional
dependency installation in `scripts/common_startup.sh` when it uses `uv`
(pip doesn't support overrides).

`tensorflow` 2.16 and later use Keras 3, which calls a layer's `call()`
without the `training` argument when building a functional model, so
`create_transformer_model()` failed with:

```
  File "lib/galaxy/tools/recommendations.py", line 118, in create_transformer_model
    x, weights = transformer_block(x)
                 ^^^^^^^^^^^^^^^^^^^^
  File ".../site-packages/keras/src/utils/traceback_utils.py", line 122, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/usr/lib/python3.11/inspect.py", line 3195, in bind
    return self._bind(args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/inspect.py", line 3110, in _bind
    raise TypeError(msg) from None
TypeError: missing a required argument: 'training'
```

Give `TransformerBlock.call()`'s `training` argument a default of `False`.
With this, loading the default tool recommendation model
(`tool_recommendation_model_v_0.2.hdf5`) with `tensorflow` 2.21.0 on
Python 3.11 and 3.13 gives the same predictions as with 2.15.1 (scores
within 6e-8).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 21:57:54 +00:00
Nicola Soranzo b86e88720c Drop support for Python 3.10
Python 3.10 reached its end-of-life in October 2026.

Also:
- Run `make pyupgrade` and `make format`
- Fix new ruff and mypy errors
- Run `uv lock` and `sh lib/galaxy/dependencies/update.sh --export-only`
- Run `make update-client-api-schema`
2026-11-17 21:57:50 +00:00
John Chilton f80b877ca1 Merge pull request #24509 from bernt-matthias/pgcleanup-delete-library-datasets
Restore the library half of the legacy delete_datasets cleanup
2026-11-02 13:21:48 -05:00
Nicola SoranzoandClaude Opus 5.5 b603e2c2fa Fix useless expressions flagged by flake8-bugbear B018 and B044
flake8-bugbear 26.10.27 now reports these expressions, whose result is
discarded, so they never did what they were meant to:

```
./lib/galaxy/datatypes/genetics.py:1153:21: B018 Found useless Call expression. Consider either assigning it to a variable or removing it.
./lib/galaxy/datatypes/genetics.py:1155:21: B018 Found useless Call expression. Consider either assigning it to a variable or removing it.
./lib/galaxy/datatypes/genetics.py:1160:21: B018 Found useless Call expression. Consider either assigning it to a variable or removing it.
./lib/galaxy/tool_util/deps/brew_exts.py:379:9: B018 Found useless GeneratorExp expression. Consider either assigning it to a variable or removing it.
./lib/galaxy_test/api/test_workflows.py:950:9: B018 Found useless Call expression. Consider either assigning it to a variable or removing it.
./lib/galaxy_test/api/test_workflows.py:961:9: B018 Found useless Call expression. Consider either assigning it to a variable or removing it.
./lib/galaxy_test/api/test_workflows.py:969:9: B018 Found useless Call expression. Consider either assigning it to a variable or removing it.
./scripts/cleanup_datasets/pgcleanup.py:1434:13: B018 Found useless Call expression. Consider either assigning it to a variable or removing it.
./test/unit/tool_util/verify/test_asserts.py:1096:5: B044 `assert <non-empty string>` is always true. Did you forget the condition?
```

`map()` and generator expressions are lazy, so replace them with `for`
loops. This means code that never ran before now runs:

- `DataIn.sniff()` now actually checks that the tokens of the first 3
  lines are numeric.
- `EnvAction.build_env()` now actually applies the environment actions.
- `Cleanup` in `pgcleanup.py` now logs the documentation lines of each
  action.
- The assertions in `TestWorkflowsApi.test_update` now run. The test
  moved every step to position `(1, 1)`, but Galaxy normalises step
  positions so that the minimum left and top are 0, so they came back
  as `(0, 0)`. Use distinct, already normalised positions instead, and
  check at the end that the original positions are restored, instead
  of modifying the downloaded steps again.

The B044 assertion in `test_asserts.py` was missing its `in a`
condition; with it added, the expected message also needed the archive
member prefix.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 03:15:41 +00:00
John ChiltonandClaude Opus 5.5 7c10754f4f Report only library datasets delete_library_datasets changed
Under --force-retry, already-reconciled rows were logged as acted on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 16:21:20 -04:00
John ChiltonandClaude Opus 5.5 425d506d41 Purge NULL-purged library datasets under --force-retry
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 16:21:20 -04:00
Matthias Bernt 7aa5ec6415 Restore the library half of the legacy delete_datasets cleanup
`pgcleanup.py` replaced `cleanup_datasets.py` in ba83310d53, but only the
dataset half of the legacy `delete_datasets()` was ported. The library half
(cleanup_datasets.py:407-440) is what marks every version of a deleted library
dataset as deleted before the library_dataset is purged, and `DeleteDatasets`
still documents that precondition ("all marked as deleted (LDDA) or purged
(HDA)").

Nothing else sets `ldda.deleted` today: the API only flags
`library_dataset.deleted` (services/library_contents.py:213,
api/library_datasets.py:362-368), so `DeleteDatasets` vetoes forever on any
dataset referenced by a library association and `PurgeDatasets` never sees the
row. Datasets that only live in libraries are therefore never cleaned up.

Add the missing `delete_library_datasets` action as a port of the legacy
behaviour, keeping legacy semantics deliberately: it marks the versions
deleted and purges the library dataset, so a purged library dataset can no
longer be undeleted (see the follow-up about enforcing that in the API).
`--force-retry` reconciles rows the legacy scripts left behind, i.e. library
datasets that are purged while their versions were never marked deleted.

`ldda.update_time` is intentionally not stamped so that
`delete_library_datasets delete_datasets purge_datasets` can be chained in a
single run; the retention decision is made on `library_dataset.update_time`,
as in the legacy script.

The folder/library halves of the legacy script (_purge_folder, purge_libraries)
are not included here.
2026-10-27 14:29:30 +00:00
mvdbeek 63eb3d9994 Stage only tracked package files in release commits
An untracked packages/uv.lock left over from before the root uv workspace was committed into the 26.2.rc1 version bump.
2026-10-14 10:52:25 +02:00
mvdbeek 3964877449 Forward-merge point releases into the next existing release branch
release_25.1 now merges into release_26.0 instead of looking for release_25.2 and falling back to dev.
2026-10-14 10:49:03 +02:00
mvdbeek 323fc0c838 Allow setting the next release version when creating a release branch
Galaxy does not always follow a release with a minor increment (26.2 is followed by 27.0), so `make release-create-rc RELEASE_NEXT=27.0` passes the dev version to release.sh via the new -n option.
2026-10-14 10:49:02 +02:00
Marius van den Beek 33b8e9749e Merge pull request #23832 from jmchilton/page_markdown_cell_types
Small fixes to Markdown fence type handling.
2026-10-05 09:49:39 +02:00
John ChiltonandClaude Opus 5.5 0f9a0b56fc Type markdown_directives_doc.py
TypedDicts mirror the directive metadata interfaces in directives.ts;
passes mypy --strict.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-30 10:58:00 -04:00
John ChiltonandClaude Opus 5.5 530601f9af Generate markdown cell types from directives.yml
Backend validator and client editor read one list; a SectionWrapper test
replaces the regex scrape of the .vue file.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-30 10:34:05 -04:00
John ChiltonandClaude Opus 5.5 edcba67701 Replace PlantUML with Mermaid in dev docs
Move the tool state diagrams into a new doc/source/dev/tool_state.md
rendered by sphinxcontrib-mermaid, updating the state representations
to match galaxy.tool_util.parameters.state. Drop the PlantUML sources,
committed SVGs, jar-downloading image.Makefile and the dead
docs-slides targets and scripts/slideshow (doc/source/slideshow was
removed in 2019).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-29 10:44:54 -04:00
Marius van den Beek e0d8cedae5 Merge pull request #23427 from bgruening/purge_oidc_when_user_is_purged
remove the OIDC link to users as well, when users are purged
2026-09-03 08:43:03 +02:00
Nicola Soranzo 0f0da08ef2 Merge branch 'release_26.1' into dev 2026-09-02 19:48:04 +01:00
mvdbeek 4edb8554ae Add script to refresh vendored IEEE-2791 schemas
Re-fetches the schema set by walking the top-level schema's $refs and
verifies each response parses as JSON (the host's WAF can serve
challenge HTML with a 200 status). The README points to it so the
vendored files aren't edited by hand. Running it today reproduces the
vendored files byte for byte.
2026-09-02 14:40:03 +02:00
Bjoern Gruening 4972384cea remove the OIDC link to users as well, when users are purged 2026-09-01 21:07:42 +02:00
John ChiltonandClaude Opus 5 605c4aec2a Merge branch 'release_26.1' into dev
Conflict: packages/tool_util/setup.cfg was deleted on dev by the
pyproject.toml migration (c329529e51) and modified on release_26.1 by
#23256, which moved jsonschema from install_requires to the test extra.
Kept the deletion and ported that move into packages/tool_util/pyproject.toml
so the dependency change isn't lost in the merge forward.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-11 16:17:23 -04:00
mvdbeek c6aec7ace5 Bound the prebuilt client on the release version instead of decrementing
The patch decrement only made sense for release-branch versions like
26.1.2.dev0. On dev the version is two-component (26.2.dev0), so the
decrement landed on the minor, and at 27.0.dev0 it produced 27.-1, which
pip rejects -- reintroducing the hard failure this is meant to remove.

Let the resolver pick the most recent published release below the current
version instead. Release candidates get the same treatment, since release
branches are cut straight to rc and sit there for weeks.

The bound uses the version with the .dev/rc suffix stripped: a bound that
is itself a prerelease would turn on prerelease matching and expose the
stray prerelease wheels on PyPI.
2026-08-06 17:02:20 +02:00
mvdbeek dcce657a0c Allow prebuilt clients for development versions
Planemo enables GALAXY_INSTALL_PREBUILT_CLIENT when serving Galaxy, so rejecting development versions breaks planemo serve against development branches.

Only tagged galaxy-web-client releases are published and they generally differ only slightly from the corresponding Galaxy development branch. Warn about that mismatch and install the preceding patch release for development versions, while continuing to pin tagged Galaxy versions exactly.
2026-08-05 14:34:51 +02:00
mvdbeek a05c2c22d4 Resolve conditional dependencies from tool_shed.yml for the Tool Shed
common_startup.sh resolved only galaxy.yml, so a Tool Shed deployment
installed nothing from conditional-requirements.txt. That is why the
sentry-sdk>=2.63.0 pin never reached toolshed.test, which kept an older
sentry-sdk and hit the FastAPI >= 0.137 wrapper-loop crash: sentry
re-wraps dependant.call on every request there, and inspect.unwrap
raises once the chain passes the recursion limit.

Move the machinery and the app-agnostic checks into
BaseConditionalDependencies so the Tool Shed evaluates the database
driver and sentry-sdk checks against its own config section, and let
run_tool_shed.sh select it with GALAXY_CONDITIONAL_DEPENDENCIES_APP.
Galaxy-only checks stay on ConditionalDependencies, where check() keeps
treating a missing check_<name> method as "not needed".
2026-07-30 12:45:42 +02:00
Marius van den Beek 8a3067d776 Merge pull request #23067 from mvdbeek/store-infra
Add pluggable tool source store infrastructure
2026-07-15 10:31:32 +02:00
mvdbeek 4896b7c08e source store: ship the populator as a galaxy-app console script 2026-07-14 19:05:51 +02:00
mvdbeek 761e43d544 Relocate tool_source_store to galaxy.tools.source_store
The package is app-coupled (galaxy.model, galaxy.config, galaxy.queues,
galaxy.datatypes) and only consumed from app-side code, so it belongs
under galaxy.tools rather than a new top-level package. Riding the
existing packages/app tools symlink also removes the need for a
dedicated package symlink. Also drop an unused back-compat alias and
fix stale doc references.

Claude-Session: https://claude.ai/code/session_018L7ZmCv2ubKA3JNeSL8Pkr
2026-07-13 10:26:59 +02:00
mvdbeek 8162853207 Add pluggable tool source store infrastructure
Introduces galaxy.tool_source_store: a queryable store of parsed,
macro-expanded tool sources plus a pre-computed ToolIndex of the metadata
batch consumers need (panel section, labels, EDAM, requirements, test
counts, shed provenance).

- Backends: database (store-owned tool_source_record + tool_index tables,
  migration f5a73c8b9d12), sqlalchemy (read-only SQLite bundles, e.g.
  CVMFS-shipped), and a composite that layers named stores over the
  default with read fall-through.
- scripts/tool_source/populate_store.py walks tool_conf files and writes
  sources + index + whoosh search index; --watch updates the store on
  file changes and broadcasts reload_tool_source_cache. The populator is
  the single writer; consumers are read-only.
- Per-conf opt-in via store="name" on a toolbox conf root, resolved
  against the tool_source_stores catalog in galaxy.yml.
- The tool_source_record table is deliberately separate from tool_source,
  whose rows belong to the job-request path and carry a raw-string
  payload contract.

Nothing reads from the store yet — an on-demand-loading toolbox consuming
it is follow-up work (#22633). Extracted from that PR.
2026-07-13 10:26:57 +02:00
John ChiltonandClaude Opus 4.8 25db54f9ef Make directives.yml the source of truth for the directive registry
Flip the relationship between directives.yml and the Python validator: the YAML
is now authoritative and scripts/markdown_directives_doc.py generates everything
downstream of it:

- lib/galaxy/managers/_markdown_directives.py - generated VALID_ARGUMENTS,
  EMBED_CAPABLE_DIRECTIVES, SHARED_ARGUMENTS, DynamicArguments; markdown_parse
  re-exports these, staying self-contained (no YAML at runtime) so it remains
  reusable outside Galaxy (e.g. gxformat2).
- client .../Utilities/requirements.yml - generated from each directive's
  'requires', removing the hand-maintained duplicate.
- directives.md - unchanged generator, now fed by the same source.

Add _shared_arguments to directives.yml (homes 'collapse' as data). Replace the
now-tautological yml-vs-parser cross-check with internal yml validation plus a
dispatch-coverage check against markdown_util.py (the gap that hid the dead
instance_citation_bibtex directive). Guard all three generated artifacts in
test_markdown_directives_doc.py and via make client-gen-markdown-directives.

Emit the directives.md tables pre-formatted to match prettier (column padding),
so the generated reference is prettier-stable and needs no ignore entry; drop the
ineffective client/.prettierignore line for it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 17:11:29 -04:00
John ChiltonandClaude Opus 4.8 eb03be8d60 Generate Markdown directive reference from directives.yml
Enrich directives.yml into the source of truth for directive docs: per-param
type/context/default/description (via shared _parameter_sets), embeddable,
requires, category, renders; add missing instance_*_link and visualization
entries.

Add scripts/markdown_directives_doc.py to render directives.md and cross-check
the yml against markdown_parse.py (VALID_ARGUMENTS, EMBED_CAPABLE_DIRECTIVES,
SHARED_ARGUMENTS) + requirements.yml. Guard via test_markdown_directives_doc.py
and `make client-gen-markdown-directives`, mirroring config-rebuild. directives.md
is generated, so prettier-ignore it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-07 14:38:39 -04:00
mvdbeek 6d4eb20906 Merge branch 'release_26.1' into dev 2026-07-06 16:12:10 +02:00
mvdbeek a3750b0326 Merge branch 'release_26.0' into release_26.1 2026-07-06 15:49:42 +02:00
paperbenni bec3d3ad9c Drop support for Python 3.8
Drop Python 3.8 support in 5 Pulsar-compatible packages
(job_metrics, tool_util, tool_util_models, util, objectstore)
and run pyupgrade --py310-plus on their source code.

- Bump requires-python from >=3.8 to >=3.10 in all 5 packages
- Remove Python 3.8 and 3.9 classifiers
- Remove ruff per-file-ignores for UP rules on these paths
- Remove backports.zoneinfo conditional dependency
- Remove pydyf<0.11 pin from conditional-requirements.txt
- Update Makefile pyupgrade target (remove PY38_PYUPGRADE_PATHS)
- Update CI workflow to test with Python 3.10 instead of 3.8

Clean up unused deprecated typing imports after pyupgrade

Remove now-unused typing imports (Dict, List, Optional, Set, Tuple,
Type, Union) that became dead after pyupgrade --py310-plus converted
annotations to use built-in types and | syntax.

Also run ruff check --fix --select=UP007,UP045 across the entire
codebase to convert remaining Optional[X] -> X | None and
Union[X, Y] -> X | Y patterns.

Enable ruff UP007/UP045 for Python 3.10 union syntax

Remove UP007 (Union[X,Y] -> X | Y) and UP045 (Optional[X] -> X | None)
from the ruff ignore list and convert all type aliases across the
codebase. These rules were deferred while Python 3.9 was supported;
requires-python is now >=3.10.

A custom script was used because neither ruff --fix nor
pyupgrade --py310-plus converts Optional[X]/Union[X,Y] in type alias
positions (e.g. X = Union[A, B]) — they only handle annotation
positions (e.g. def f(x: Optional[int])). All 167 violations were
module-level type aliases. A few edge cases were fixed manually:
single-element Union[X,], typing.Union qualified refs, runtime
Optional[type] calls, and Annotated[Optional[...]] pydantic fields.

Fix UP007 autofix regression with string forward reference type aliases

Commit fa6bd955a0 enabled ruff UP007/UP045 and auto-fixed
module-level type aliases using Union with string forward
references, producing invalid 'str | str' expressions.

This was a known ruff bug (charliermarsh/ruff#826) that has since
been fixed in later ruff versions, but this codebase was
converted before the fix was in place.

Revert to Union syntax and restore TYPE_CHECKING imports that
ruff's TCH rule cleaned up as a side effect when it thought the
forward references were unused.
2026-06-25 15:12:05 +01:00
Björn Grüning 7be9e24e17 Remove duplicate clear call in remove_objects method
Removed redundant call to clear objects_to_remove.
2026-06-10 03:04:38 +02:00
davelopez a66ec96dfe Prevent deletion of user-defined object stores
Skips the physical file removal process for datasets stored in user-defined object stores. These storage locations cannot be resolved by the cleanup script, so the database records are updated while the external files remain intact to prevent potential errors or data loss.
2026-06-08 12:41:24 +02:00
Bjoern Gruening 310c7795fd implement batch-size 2026-06-06 16:09:42 +02:00
Bjoern Gruening 8a6f311c6b try to optimize the purge_historyless_hdas case 2026-06-05 04:42:52 +02:00
mvdbeek df4b4c8a12 Address gx-arch-review feedback on PR #22212
- Extract FavoritesManager (lib/galaxy/managers/favorites.py): owns
  normalize / resolve / persist / order logic; controllers in users.py
  are now 2 lines each, and trans.sa_session.commit moves out of the
  controller layer. Drops the redundant re-normalize on every write
  and replaces FavoriteObjectType.X.value == .value defensive dispatch
  with enum-identity comparison. Renames the set_favorite_order
  endpoint summary away from the ambiguous "top-level" wording.
- Move curated_tool_tags_by_id off the toolbox into ToolsService;
  the controller now routes through the service instead of poking
  trans.app.toolbox directly. Raw aggregates (curated_tool_tags,
  tool_edam_operations, tool_edam_topics) remain on the toolbox since
  they're derived from per-tool data.
- Rename /api/tools/tags -> /api/tags/tool_tags (operation_id
  tags__tool_tags) to disambiguate from /api/tools/{id}; update the
  client store, tests, and the hand-edited OpenAPI schema entry.
  (Run `make update-client-api-schema` before pushing to regenerate
  the schema in its canonical alphabetical position.)
- Promote inline imports to module-level (ontology_data.py logging,
  app/__init__.py configure_tool_tag_mapping); replace
  getattr(self.config, "tool_tag_mappings_file", None) with direct
  attribute access now that the option is registered in the schema.
- Convert ontology_data's import-time bundled-mapping reads to
  lru_cache so the YAML / TSV files load lazily; fix the
  Tool._setup_id comment to point at the actual lowercasing site
  (Tool.parse around `self_ids = [self.id.lower()]`).
- doc/source/admin/tool_panel.rst: 26.0 -> 26.1.
- scripts/extract_tool_sections_from_api.py: annotate the public
  helpers the test suite imports.
- test_to_dict_cache_drops_when_tool_removed now asserts observable
  to_dict() output before/after remove, not private cache membership.
- Split test_tool_discovery_landing into focused tests; extract a
  helper that opens the discovery view and types the standard filter.
- Move the Playwright drag helper from test_tool_panel_search.py into
  TestWithSeleniumMixin.playwright_drag_item_above so future tests
  reuse it.
- Client tests: drop the full-string Whoosh equality in
  utilities.test.ts; hard-code expected Whoosh strings in
  ToolsList.test.ts (drop createWhooshQuery as both sides of the
  assertion) and remove the redundant injectTestRouter mount option
  (ToolsList.vue only uses the useRouter composable); drop the
  FontAwesome data-icon/iconName assertions in ToolPanel.test.ts in
  favor of icon-existence checks; replace three near-identical
  add/remove favorite tests in ToolsListCard.test.ts with an it.each;
  export quoteToolTagValue from Panels/utilities so
  filterConversion.test.js imports the real helper instead of
  reconstructing it inline; delete the spy-only "loads the curated
  tag mapping" test in ToolBoxSearch.test.ts (the gate is covered by
  ToolPanel.test.ts's negative case and the favorite-tag rendering
  tests cover the positive case end-to-end).
2026-05-19 11:43:34 +02:00
Bjoern Gruening 70d9c89eb2 Harden extract_tool_sections_from_api script and document curated tags
Two related fixes around the admin-facing helper script and admin docs:

* Make the helper script work from any cwd and against any Galaxy
  server: `--api-url`, `--output`, `--timeout` argparse flags; raise
  `RuntimeError` on transport / decode failures (was a silent no-op);
  anchor the default output path on the script location so
  `python scripts/extract_tool_sections_from_api.py` works without a
  prior `cd`. Default output now points at `config/tool_tag_mappings.yml`
  to match the new admin override path.

* Add a "Curated tool tags" section to `doc/source/admin/tool_panel.rst`
  documenting the new `tool_tag_mappings_file` option, the new
  `tag:"…"` / `ontology:"…"` search syntax, the `?section=` URL
  deprecation, and the reindex requirement after changing the mapping.
2026-05-07 13:23:33 +02:00
Bjoern Gruening 193abcf738 second iteration of the personalized tool panel 2026-05-07 13:09:36 +02:00
Dannon Baker da911d0cf3 Restructure client build-state check to match the build block
Nest the prebuilt/hash-check branches inside `if [ $SKIP_CLIENT_BUILD
-eq 0 ]` so the shape mirrors the subsequent build-or-install block.
Per Nicola's review.
2026-04-17 14:53:24 -04:00
DannonandNicola Soranzo 693486432a Update scripts/common_startup.sh
Co-authored-by: Nicola Soranzo <nicola.soranzo@gmail.com>
2026-04-17 14:51:56 -04:00
Dannon Baker ab245fbb79 Install prebuilt client from PyPI wheel instead of npm
The prebuilt client path (GALAXY_INSTALL_PREBUILT_CLIENT=1, used by
planemo) now pulls the matching galaxy-web-client wheel from PyPI and
lets webapp.py pick it up via `import galaxy.web_client`. The
root-level pnpm install is no longer needed for this flow -- the
Galaxy client isn't a JS library, so shipping it as an npm package
was always the wrong shape.

Dev versions don't have a published wheel, so we bail early with a
message pointing users at the source build path.
2026-04-17 11:19:21 -04:00
Dannon Baker c57aaeb96c Drop --frozen-lockfile from prebuilt client install
No root pnpm-lock.yaml is shipped, so `pnpm install --frozen-lockfile`
fails with ERR_PNPM_NO_LOCKFILE (hit locally via planemo). The dev
branch is unaffected -- client/pnpm-lock.yaml exists.
2026-04-16 17:30:10 -04:00
Michael R. Crusoe dbfcdb8bc9 python packages: convert to pure namespace packages
only directories in `lib/galaxy` & `packages/*/galaxy`
All other files removed or moved to their own module
All references to those files updated, especially galaxy/version.py
2026-04-15 15:16:34 +02:00
Nicola Soranzo d31114bdaa Migrate 3 scripts from psycopg2 to SQLAlchemy 2026-03-25 20:18:39 +00:00
mvdbeek d77ed6e740 Merge branch 'release_26.0' into dev 2026-03-11 10:22:01 +01:00
mvdbeek 8ac4b81b79 Fix repo metadata persistence in fix_tool_config_paths.py 2026-03-09 15:09:45 +01:00
Uwe WinterandNicola Soranzo afd4d3f526 Update scripts/common_startup.sh
Co-authored-by: Nicola Soranzo <nicola.soranzo@gmail.com>
2026-02-11 22:05:43 +11:00
Uwe Winter aa53fe3c3b fix: system uv can select a different python version than in the conda environment 2026-02-10 11:23:43 +11:00