Skip to content

Conversation

@rjernst
Copy link
Member

@rjernst rjernst commented Aug 13, 2025

The build system for transport versions operate on two different types of projects. A project can have named references to transport versions, and it could also be the source of truth for transport version resources, where latest and definitions files exist. This commit renames the plugins and tasks to consistently use that terminology.

…elastic#132882)

The build system for transport versions operate on two different types
of projects. A project can have named references to transport versions,
and it could also be the source of truth for transport version resources,
where latest and definitions files exist. This commit renames the
plugins and tasks to consistently use that terminology.
@rjernst rjernst added backport auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) labels Aug 13, 2025
@elasticsearchmachine elasticsearchmachine merged commit 3c5698b into elastic:8.19 Aug 14, 2025
22 checks passed
@rjernst rjernst deleted the transport/terminology_cleanup_8.19 branch August 14, 2025 00:51
albertzaharovits pushed a commit to albertzaharovits/elasticsearch that referenced this pull request Aug 14, 2025
…elastic#132882) (elastic#132898)

The build system for transport versions operate on two different types
of projects. A project can have named references to transport versions,
and it could also be the source of truth for transport version resources,
where latest and definitions files exist. This commit renames the
plugins and tasks to consistently use that terminology.
elasticsearchmachine pushed a commit that referenced this pull request Aug 15, 2025
…132913)

* There must be at least one merge task blocked (#132496)

After triggering a force merge, there might still be other merge tasks
running concurrently, so it is incorrect to assert a single merge is
blocked in the test.

Fix #131789

Co-authored-by: Patrick Doyle <[email protected]>

* Use consistent terminology for transport version resources/references (#132882) (#132898)

The build system for transport versions operate on two different types
of projects. A project can have named references to transport versions,
and it could also be the source of truth for transport version resources,
where latest and definitions files exist. This commit renames the
plugins and tasks to consistently use that terminology.

---------

Co-authored-by: Patrick Doyle <[email protected]>
Co-authored-by: Ryan Ernst <[email protected]>
szybia added a commit to szybia/elasticsearch that referenced this pull request Aug 15, 2025
* upstream/8.19: (62 commits)
  Use consistent terminology for transport version resources/references (elastic#132882) (elastic#132898)
  Move inner records out of TransportVersionUtils (elastic#132872) (elastic#132886)
  Forward port release notes for v8.18.5 (elastic#132758)
  Add more transport version files validation (elastic#132373) (elastic#132777)
  Forward port release notes for v8.17.10 (elastic#132760)
  Refactor TransportVersion loading to support external consumers (elastic#132694) (elastic#132862)
  manual backporting| (elastic#132783)
  9.1 docs backports for 8.19 features (elastic#132605)
  Migrate x-pack-deprecation REST tests (elastic#131444) (elastic#132802)
  Update 8.19.1.asciidoc (elastic#132755)
  Update wolfi (versioned) (elastic#132752)
  Update 8.19.0.asciidoc (elastic#132754)
  Prune changelogs after 8.19.2 release
  Bump versions after 8.19.2 release
  Finalize release notes for v8.19.2
  Bump versions after 8.17.10 release
  Prune changelogs after 8.18.5 release
  Bump versions after 8.18.5 release
  Add release notes for v8.19.2 release (elastic#132696)
  [ML] Improve EIS auth call logs and fix revocation bug (elastic#132546) (elastic#132690)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v8.19.3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants