#3271 chore: Make AAPL fundamentals tap a dev package Pull request opened by edgarrmondragon ## Summary by Sourcery Introduce a new tap-fundamentals development package for AAPL fundamentals by relocating sample code into a standalone workspace package, adding project configuration, and refining code structure and tooling. New Features: • Add tap-fundamentals package with CLI entry point and bundled AAPL JSON data Enhancements: • Centralize schema directory loading via importlib.resources and apply consistent type hints with conditional override imports • Refactor stream class methods to use @OverRide decorator and explicit type annotations Build: • Include tap-fundamentals in the workspace pyproject.toml and define its own project metadata and dependencies CI: • Update pre-commit configuration to exclude JSON files in packages from codespell checks Chores: • Remove legacy samples/aapl directory and its init file • Regenerate uv.lock to reflect the new package meltano/sdk

#3272 chore: Release v0.49.0 Pull request opened by MeltyBot Prepare MeltanoSDK

v0.49.0

for release. Checklist: • Check that the right version is set in all the files. • Groom the changelog for wording or missing entries. • Merge this PR once everything looks good. Release Draft ## Summary by Sourcery Prepare MeltanoSDK v0.49.0 release by updating the changelog, bumping version references, and incorporating new features, fixes, and under-the-hood improvements New Features: • Default ObjectType fields now use additionalProperties: true • Use ty to check types in tap, target, and mapper templates Bug Fixes: • Add DecimalType alias for NumberType Enhancements: • Move all SQLAlchemy-related classes to singer_sdk.sql, deprecate old locations, and add a sql dependency extra • Deprecate the stream attribute in authenticator constructors and the create_for_stream method • Adopt typing.override in mapper and tap templates • Remove unused plugin_type attribute from test template classes • Convert relevant classes to slotted dataclasses Build: • Drop support for Python 3.9 • Bump singer-sdk dependency to v0.49.0 across cookiecutter templates, example packages, and the root project • Update commitizen version to 0.49.0 Documentation: • Update docs landing page and add link to the contribution guide meltano/sdk

Release - v0.49.0 New release published by edgarrmondragon ## v0.49.0 (2025-09-11) ### ✨ New • #3262 By default

ObjectType

fields now use

additionalProperties: true

• #3196 Use

ty

to check types in tap, target and mapper templates ### 🐛 Fixes • #3257 Add

DecimalType

alias for

NumberType

### ⚙️ Under the Hood • #3269 Move all SQLAlchemy-related classes to

singer_sdk.sql

, deprecate old locations and add a

sql

dependency extra • #3268 Deprecate the

stream

attribute in authenticator constructors and also deprecate the

create_for_stream

method • #3267 Use

typing.override

in mapper and tap templates • #3177 Remove unused

plugin_type

attribute from test template classes • #3253 Use slotted dataclasses ### 📚 Documentation Improvements • #3258 Update docs landing page • #3254 Link to https://github.com/meltano/sdk/contribute ### 📦 Packaging changes • #3252 Dropped support for Python 3.9 meltano/sdk

#9496 packaging: Restore support for Click 8.1 Pull request opened by edgarrmondragon It's compatible (tested it) with only a few typing caveats, which are not user-facing. This is required for the next Meltano to work with Dagster, since it doesn't allow Click 8.2: • dagster-io/dagster@32720dd • https://github.com/dagster-io/dagster/blame/ef5bd6d0d2149613f56f9a5bc0f2f2a0a9a327a1/python_modules/dagster/setup.py#L84 The alternative would be to wait for Dagster to move up their constraint: • dagster-io/dagster#32144 ## Description ## Related Issues • Closes #XXXX ## Summary by Sourcery Build: • Restore support for Click 8.1 by adjusting the click dependency constraint meltano/meltano

#9497 chore: Use colors from meltano.com for readme badges Pull request opened by edgarrmondragon ## Description SSIA. ## Related Issues • Closes #XXXX ## Summary by Sourcery Unify README badges with Meltano brand colors and update badge layout Documentation: • Use Meltano brand colors for all README shields and unify badge styling • Add a Slack community badge and reorganize badge sections into centered groups • Convert section headings to ATX-style '##' headings for consistency meltano/meltano

#3273 chore: Use colors from meltano.com for readme badges Pull request opened by edgarrmondragon ## Summary by Sourcery Unify README badges with Meltano brand colors and standardize their labels and endpoints Documentation: • Update all README shields to use Meltano brand colors by adding labelColor and color parameters • Replace Read the Docs and Codecov badges with shields.io endpoints • Standardize alt text and URL formatting for all badges Chores: • Fix italic formatting for the "Not familiar with Meltano?" line meltano/sdk

#3410 Confusing log messages when setting/unsetting password settings Issue created by MeltyBot Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3492 Originally created by @kgpayne on 2022-05-16 151513 --- ### What is the current bug behavior? What is happening now? When setting and then unsetting password kind settings, the behaviour appears to be correct but the logs and messages returned are conflicting/confusing. ### What is the expected correct behavior? What should be happening? • The

set

command should not output warnings about keys that cannot be removed • The

unset

command should output a clear and consistent output message (it unsets all stores where a setting is defined). ### Steps to reproduce How one can reproduce the issue? meltano add extractor tap-gitlab # produces erroneous warnings, but works as expected (value set in .env file) meltano config tap-gitlab set private_token "test 2" # 2022-05-16T142811.512972Z [warning ] Key GITLAB_API_TOKEN not removed from /Users/kp/Projects/demo/interactive-test/.env - key doesn't exist. # Extractor 'tap-gitlab' setting 'private_token' was set in `.env`: 'test 2' # produces erroneous warnings, but appears to work as expected (clears value in .env file) meltano config tap-gitlab unset private_token # 2022-05-16T142857.383895Z [warning ] Key GITLAB_API_TOKEN not removed from /Users/kp/Projects/demo/interactive-test/.env - key doesn't exist. # Extractor 'tap-gitlab' setting 'private_token' in the system database was unset ### Relevant logs and/or screenshots Please use code blocks (```) to format console output ### Possible fixes If you can, link to the line of code that might be responsible for the problem or suggest a fix ### Further regression test Ensure we automatically catch similar issues in the future • Write additional adequate test cases and submit test results • Test results should be reviewed by a person from the team @tayloramurphy @aaronsteers FYI as this may be desirable to fix, or at least investigate further, for 2.0 meltano/meltano

#6281 Windows - Test with backend databases other than SQLLite Issue created by visch We struggled getting docker to work with a Windows github action • #6155 , specifically #6155 (comment) Ideally we'd test Windows with Postgres, and other Database backends meltano/meltano

#6151 docs: MacOS installation instructions needs XCode install steps added Issue created by visch MacOS requires that XCode be installed to some extend. I'm not sure exactly what does / does not need to be installed but many folks hit issues with this when installing Meltano while using a Mac. meltano/meltano

#9498 feat(cli): Log a more detailed reason for skipping a plugin's installation Pull request opened by edgarrmondragon ## Description For this project version: 1 default_environment: dev environments: - name: dev plugins: extractors: - name: tap-fedidb variant: edgarrmondragon pip_url: tap-fedidb - name: tap-fedidb--child inherit_from: tap-fedidb the output is $ meltano install 2025-09-12T173925.308381Z [info ] Installing 2 plugins 2025-09-12T173925.308623Z [info ] Skipped installing extractor 'tap-fedidb--child'. Plugin 'tap-fedidb--child' does not require installation: reusing parent virtualenv. 2025-09-12T173925.315321Z [info ] Installing extractor 'tap-fedidb' 2025-09-12T173925.462257Z [info ] Installed extractor 'tap-fedidb' 2025-09-12T173925.462751Z [info ] Installed 1/2 plugins 2025-09-12T173925.462841Z [info ] Skipped installing 1/2 plugins And for this project version: 1 default_environment: dev environments: - name: dev plugins: extractors: - name: tap-fedidb variant: edgarrmondragon pip_url: tap-fedidb - name: tap-fedidb--child pip_url: tap-fedidb python-json-logger # notice this is different inherit_from: tap-fedidb this is the output $ meltano install 2025-09-12T174130.763630Z [info ] Installing 2 plugins 2025-09-12T174130.770836Z [info ] Installing extractor 'tap-fedidb' 2025-09-12T174130.784475Z [info ] Installing extractor 'tap-fedidb--child' 2025-09-12T174130.855497Z [info ] Installed extractor 'tap-fedidb--child' 2025-09-12T174130.855824Z [info ] Installed extractor 'tap-fedidb' 2025-09-12T174130.855945Z [info ] Installed 2/2 plugins ## Related Issues • Closes #6501 ## Summary by Sourcery Use pattern matching for install status handling and enhance skip logic to include explicit reasons in logs New Features: • Log detailed skip reasons when a plugin’s installation is skipped Enhancements: • Refactor plugin status verb resolution and logging to use pattern matching • Update _requires_install to return a message describing why installation was skipped • Streamline plugin install summary by introducing a total count for reporting meltano/meltano

#6501 bug: Confusing meltano install logs for inherited and container-based plugins Issue created by larskoe ### Meltano Version 2.3.0 ### Python Version 3.8 ### Bug scope CLI (options, error messages, logging, etc.) ### Operating System MacOS - 12.4 ### Description When running

meltano install

, it'll say skipped for the inherited plugins. This is confusing as it indicates they aren't being installed (see screenshot below). ### Code No response meltano/meltano

#3274 chore: Unpin `singer-sdk` in local packages Pull request opened by edgarrmondragon This should make it easier to add them to any project. ## Summary by Sourcery Unpin singer-sdk dependency across all local packages for greater flexibility and update versioning files accordingly Enhancements: • Remove strict version requirement for singer-sdk in all packages Chores: • Remove singer-sdk version pin from packages’ pyproject.toml files • Delete version_files entry for singer-sdk in root pyproject.toml • Regenerate lockfile to reflect unpinned singer-sdk dependency meltano/sdk

#3275 fix: Add setter method to deprecated `APIAuthenticatorBase.tap_name` property Pull request opened by edgarrmondragon ## Summary by Sourcery Add a setter for the deprecated tap_name property to allow updating its value Enhancements: • Add tap_name.setter method to enable setting the deprecated tap_name property • Simplify the tap_name getter docstring meltano/sdk

#3276 chore: Release v0.49.1 Pull request opened by MeltyBot Prepare MeltanoSDK

v0.49.1

for release. Checklist: • Check that the right version is set in all the files. • Groom the changelog for wording or missing entries. • Merge this PR once everything looks good. Release Draft ## Summary by Sourcery Prepare and release version 0.49.1 with a bug fix for APIAuthenticatorBase.tap_name and version updates across project files Bug Fixes: • Add setter method to deprecated APIAuthenticatorBase.tap_name property (#3275) Chores: • Bump SDK dependency versions in cookiecutter templates to 0.49.1 • Update project version strings in CHANGELOG, pyproject.toml, docs/conf.py, ISSUE_TEMPLATE, and commitizen config meltano/sdk

Release - v0.49.1 New release published by edgarrmondragon ## v0.49.1 (2025-09-14) ### 🐛 Fixes • #3275 Add setter method to deprecated

APIAuthenticatorBase.tap_name

property meltano/sdk

#9499 ci: Bump the actions group with 2 updates Pull request opened by dependabot[bot] Bumps the actions group with 2 updates: astral-sh/setup-uv and github/codeql-action. Updates

astral-sh/setup-uv

from 6.6.1 to 6.7.0 Release notes Sourced from astral-sh/setup-uv's releases.

## v6.7.0 🌈 New inputs

restore-cache

and

save-cache

## Changes

This release adds fine-grained control over the caching steps.

• The input

restore-cache

(

true

by default) can be set to

false

to skip restoring the cache while still allowing to save the cache.

• The input

save-cache

(

true

by default) can be set to

false

to skip saving the cache.

Skipping cache saving can be useful if you know, that you will never use this version of the cache again and don't want to waste storage space:

- name: Save cache only on main branch

uses: astral-sh/setup-uv@v6

with:

enable-cache: true

save-cache: ${{ github.ref == 'refs/heads/main' }}

## 🚀 Enhancements

• Add inputs restore-cache and save-cache `@​eifinger` (#568)

## 🧰 Maintenance

• bump deps `@​eifinger` (#569)

• Automatically push updated known versions `@​eifinger` (#565)

• chore: update known versions for 0.8.16/0.8.17 @github-actions[bot] (#562)

• chore: update known versions for 0.8.15 @github-actions[bot] (#550)

• chore(ci): address CI lint findings `@​woodruffw` (#545)

## ⬆️ Dependency updates

• Bump github/codeql-action from 3.29.11 to 3.30.3 @dependabot[bot] (#566)

• Bump actions/setup-node from 4.4.0 to 5.0.0 @dependabot[bot] (#551)

Commits • `b75a909` bump deps (#569) • `ffff8aa` Bump github/codeql-action from 3.29.11 to 3.30.3 (#566) • `95d0e23` Bump actions/setup-node from 4.4.0 to 5.0.0 (#551) • `dc724a1` Add inputs restore-cache and save-cache (#568) • `f67343a` Automatically push updated known versions (#565) • `4dd9f52` chore: update known versions for 0.8.16/0.8.17 (#562) • `e1e6fe7` chore: update known versions for 0.8.15 (#550) • `b183611` chore(ci): address CI lint findings (#545) • See full diff in compare view Updates

github/codeql-action

from 3.30.1 to 3.30.3 Release notes Sourced from github/codeql-action's releases.

## v3.30.3

# CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

## 3.30.3 - 10 Sep 2025

No user facing changes.

See the full CHANGELOG.md for more information.

## v3.30.2

# CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

## 3.30.2 - 09 Sep 2025

• Fixed a bug which could cause language autodetection to fail. #3084

• Experimental: The

quality-queries

input that was added in

3.29.2

as part of an internal experiment is now deprecated and will be removed in an upcoming version of the CodeQL Action. It has been superseded by a new

analysis-kinds

input, which is part of the same internal experiment. Do not use this in production as it is subject to change at any time. #3064

See the full CHANGELOG.md for more information.

Changelog Sourced from github/codeql-action's changelog.

# CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

## [UNRELEASED]

• We have improved the CodeQL Action's ability to validate that the workflow it is used in does not use different versions of the CodeQL Action for different workflow steps. Mixing different versions of the CodeQL Action in the same workflow is unsupported and can lead to unpredictable results. A warning will now be emitted from the

codeql-action/init

step if different versions of the CodeQL Action are detected in the workflow file. Additionally, an error will now be thrown by the other CodeQL Action steps if they load a configuration file that was generated by a different version of the

codeql-action/init

step. #3099 and #3100

• We added support for reducing the size of dependency caches for Java analyses, which will reduce cache usage and speed up workflows. This will be enabled automatically at a later time. #3107

## 3.30.3 - 10 Sep 2025

No user facing changes.

## 3.30.2 - 09 Sep 2025

• Fixed a bug which could cause language autodetection to fail. #3084

• Experimental: The

quality-queries

input that was added in

3.29.2

as part of an internal experiment is now deprecated and will be removed in an upcoming version of the CodeQL Action. It has been superseded by a new

analysis-kinds

input, which is part of the same internal experiment. Do not use this in production as it is subject to change at any time. #3064

## 3.30.1 - 05 Sep 2025

• Update default CodeQL bundle version to 2.23.0. <https://…

meltano/meltano

#3277 chore(deps): bump the actions group with 3 updates Pull request opened by dependabot[bot] Bumps the actions group with 3 updates: astral-sh/setup-uv, github/codeql-action and CodSpeedHQ/action. Updates

astral-sh/setup-uv

from 6.6.1 to 6.7.0 Release notes Sourced from astral-sh/setup-uv's releases.

## v6.7.0 🌈 New inputs

restore-cache

and

save-cache

## Changes

This release adds fine-grained control over the caching steps.

• The input

restore-cache

(

true

by default) can be set to

false

to skip restoring the cache while still allowing to save the cache.

• The input

save-cache

(

true

by default) can be set to

false

to skip saving the cache.

Skipping cache saving can be useful if you know, that you will never use this version of the cache again and don't want to waste storage space:

- name: Save cache only on main branch

uses: astral-sh/setup-uv@v6

with:

enable-cache: true

save-cache: ${{ github.ref == 'refs/heads/main' }}

## 🚀 Enhancements

• Add inputs restore-cache and save-cache `@​eifinger` (#568)

## 🧰 Maintenance

• bump deps `@​eifinger` (#569)

• Automatically push updated known versions `@​eifinger` (#565)

• chore: update known versions for 0.8.16/0.8.17 @github-actions[bot] (#562)

• chore: update known versions for 0.8.15 @github-actions[bot] (#550)

• chore(ci): address CI lint findings `@​woodruffw` (#545)

## ⬆️ Dependency updates

• Bump github/codeql-action from 3.29.11 to 3.30.3 @dependabot[bot] (#566)

• Bump actions/setup-node from 4.4.0 to 5.0.0 @dependabot[bot] (#551)

Commits • `b75a909` bump deps (#569) • `ffff8aa` Bump github/codeql-action from 3.29.11 to 3.30.3 (#566) • `95d0e23` Bump actions/setup-node from 4.4.0 to 5.0.0 (#551) • `dc724a1` Add inputs restore-cache and save-cache (#568) • `f67343a` Automatically push updated known versions (#565) • `4dd9f52` chore: update known versions for 0.8.16/0.8.17 (#562) • `e1e6fe7` chore: update known versions for 0.8.15 (#550) • `b183611` chore(ci): address CI lint findings (#545) • See full diff in compare view Updates

github/codeql-action

from 3.30.1 to 3.30.3 Release notes Sourced from github/codeql-action's releases.

## v3.30.3

# CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

## 3.30.3 - 10 Sep 2025

No user facing changes.

See the full CHANGELOG.md for more information.

## v3.30.2

# CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

## 3.30.2 - 09 Sep 2025

• Fixed a bug which could cause language autodetection to fail. #3084

• Experimental: The

quality-queries

input that was added in

3.29.2

as part of an internal experiment is now deprecated and will be removed in an upcoming version of the CodeQL Action. It has been superseded by a new

analysis-kinds

input, which is part of the same internal experiment. Do not use this in production as it is subject to change at any time. #3064

See the full CHANGELOG.md for more information.

Changelog Sourced from github/codeql-action's changelog.

# CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

## [UNRELEASED]

• We have improved the CodeQL Action's ability to validate that the workflow it is used in does not use different versions of the CodeQL Action for different workflow steps. Mixing different versions of the CodeQL Action in the same workflow is unsupported and can lead to unpredictable results. A warning will now be emitted from the

codeql-action/init

step if different versions of the CodeQL Action are detected in the workflow file. Additionally, an error will now be thrown by the other CodeQL Action steps if they load a configuration file that was generated by a different version of the

codeql-action/init

step. #3099 and #3100

• We added support for reducing the size of dependency caches for Java analyses, which will reduce cache usage and speed up workflows. This will be enabled automatically at a later time. #3107

## 3.30.3 - 10 Sep 2025

No user facing changes.

## 3.30.2 - 09 Sep 2025

• Fixed a bug which could cause language autodetection to fail. #3084

• Experimental: The

quality-queries

input that was added in

3.29.2

as part of an internal experiment is now deprecated and will be removed in an upcoming version of the CodeQL Action. It has been superseded by a new

analysis-kinds

input, which is part of the same internal experiment. Do not use this in production as it is subject to change at any time. #3064

## 3.30.1 - 05 Sep 2025

•…

meltano/sdk

#9500 chore(deps): Bump types-pyyaml from 6.0.12.20250822 to 6.0.12.20250915 Pull request opened by dependabot[bot] Bumps types-pyyaml from 6.0.12.20250822 to 6.0.12.20250915. Commits • See full diff in compare view [Dependabot compatibility score](https://camo.githubusercontent.com/9d3cfae5673ce9a99e83d4d7dcd3573373f7cffb0c08f09fb49c3858e676fe9e/68747470733a2f2f646570656e6461626f742d6261646765732e6769746875626170702e636f6d2f6261646765732f636f6d7061746962696c6974795f73636f72653f646570656e64656e63792d6e616d653d74797065732d707979616d6c267061636b6167652d6d616e616765723d75762670726576696f75732d76657273696f6e3d362e302e31322e3230323530383232266e65772d76657273696f6e3d362e302e31322e3230323530393135) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot show <dependency name> ignore conditions

will show all of the ignore conditions of the specified dependency •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) meltano/meltano

#9501 chore(deps): Bump the runtime-dependencies group with 6 updates Pull request opened by dependabot[bot] Bumps the runtime-dependencies group with 6 updates: | Package | From | To | | -------------------------------------------------------------------- | ------- | ------- | | [azure-core](https://github.com/Azure/azure-sdk-for-python) | 1.35.0 | 1.35.1 | | [azure-identity](https://github.com/Azure/azure-sdk-for-python) | 1.24.0 | 1.25.0 | | [google-cloud-storage](https://github.com/googleapis/python-storage) | 3.3.1 | 3.4.0 | | [boto3](https://github.com/boto/boto3) | 1.40.29 | 1.40.30 | | [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | 1.1.0 | 1.2.0 | | [mypy](https://github.com/python/mypy) | 1.17.1 | 1.18.1 | Updates

azure-core

from 1.35.0 to 1.35.1 Release notes Sourced from azure-core's releases.

## azure-core_1.35.1

## 1.35.1 (2025-09-11)

### Bugs Fixed

• Fixed an issue where the

retry_backoff_max

parameter in

RetryPolicy

and

AsyncRetryPolicy

constructors was being ignored, causing retry operations to use default maximum backoff values instead of the user-specified limits. #42444

### Other Changes

•

BearerTokenCredentialPolicy

and

AsyncBearerTokenCredentialPolicy

will now properly surface credential exceptions when handling claims challenges. Previously, exceptions from credential token requests were suppressed; now they are raised and chained with the original 401

HttpResponseError

response for better debugging visibility. #42536

Commits • `e4fde9e` [Core] Prepare release (#42966) • `df01859` [Core] Read stream challenge error response (#42920) • `1a598ea` [Core] Chain challenge responses with token exceptions (#42536) • `9958caf` NOCI move tools/azure-sdk-tools under eng/tools and all references acr... • `6af5eaf` [Core] Fix ignored retry_backoff_max in RetryPolicies (#42444) • `61bb88f` Add logging section to azure-core README.md (#42391) • `4e688ad` Put obvious fake values for cred linter (#42124) • `0e64863` Increment package version after release of azure-core (#41887) • `4e048f8` [Mgmt Core] Prepare release (#41883) • See full diff in compare view Updates

azure-identity

from 1.24.0 to 1.25.0 Release notes Sourced from azure-identity's releases.

## azure-identity_1.25.0

## 1.25.0 (2025-09-11)

### Features Added

•

AzureDeveloperCliCredential

now supports

claims

in

get_token

and

get_token_info

. (#42568)

• Added new keyword argument

require_envvar

to

DefaultAzureCredential

to enforce the presence of the

AZURE_TOKEN_CREDENTIALS

environment variable. (#42660)

### Bugs Fixed

• Fixed an issue where

AzureDeveloperCliCredential

would time out during token requests when

azd

prompts for user interaction. This issue commonly occurred in environments where the

AZD_DEBUG

environment variable was set, causing the Azure Developer CLI to display additional prompts that interfered with automated token acquisition. (#42535)

• Fixed an issue where credentials configured with a default tenant ID of "organizations" (such as

InteractiveBrowserCredential

and

DeviceCodeCredential

) would fail authentication when a specific tenant ID was provided in

get_token

or

get_token_info

method calls. (#42721)

### Other Changes

• Updated

SharedTokenCacheCredential

to raise

CredentialUnavailableError

instead of

ClientAuthenticationError

during token refresh failures when within the context of

DefaultAzureCredential

. (#42934)

Commits • `0da8698` Make Prepare-Release.ps1 executable (#42976) • `2352685` Increment package version after release of azure-core (#42979) • `2dac85a` updated CHANGELOG.md with the release information 4.14.0b4 (2025-09-11) (#42972) • `fcc40eb` Mypy Dev Requirement Installation Fix (#42973) • `eb0ecce` [Identity] Adjust cache credential error behavior in DAC (#42934) • `95c0373` Add custom instructions to fetch TypeSpec docs (#42970) • `e150a42` Fix getting secret keys for connections of type "Custom Keys" (#42937) • `f6ac36d` Session Token Manual Override Fix (#42965) • `e4fde9e` [Core] Prepare release (#42966) • <https://github.com/Azure/azure-sdk-for-python/commit/4b71cbebb179e9ae0c83fb004904ea29cabb16f5|`… meltano/meltano

#9502 chore(deps): Bump types-requests from 2.32.4.20250809 to 2.32.4.20250913 Pull request opened by dependabot[bot] Bumps types-requests from 2.32.4.20250809 to 2.32.4.20250913. Commits • See full diff in compare view [Dependabot compatibility score](https://camo.githubusercontent.com/ed88047223cd1edeeb5beea259e1a24fcbeeae7ba60753d52bfd3a2abcc5ace3/68747470733a2f2f646570656e6461626f742d6261646765732e6769746875626170702e636f6d2f6261646765732f636f6d7061746962696c6974795f73636f72653f646570656e64656e63792d6e616d653d74797065732d7265717565737473267061636b6167652d6d616e616765723d75762670726576696f75732d76657273696f6e3d322e33322e342e3230323530383039266e65772d76657273696f6e3d322e33322e342e3230323530393133) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot show <dependency name> ignore conditions

will show all of the ignore conditions of the specified dependency •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) meltano/meltano

#9503 chore(deps): Bump pytest-randomly from 3.16.0 to 4.0.1 Pull request opened by dependabot[bot] Bumps pytest-randomly from 3.16.0 to 4.0.1. Changelog Sourced from pytest-randomly's changelog.

## 4.0.1 (2025-09-12)

• Remove the random state caching, which would grow without bound, leaking memory in long test runs. The caching was added to slightly speed up re-using the same (final) seed, but since the final seed is now different for each test, it has no effect.

`PR [#690](https://github.com/pytest-dev/pytest-randomly/issues/690) https://github.com/pytest-dev/pytest-randomly/issues/687`__.

• Modify Numpy seed restriction, replacing hashing with a modulo operation. The extra work to hash is unnecessary now that we generate a final seed per test with CRC32. This change saves ~500ns per test when Numpy is installed.

`PR [#691](https://github.com/pytest-dev/pytest-randomly/issues/691) https://github.com/pytest-dev/pytest-randomly/issues/691`__.

## 4.0.0 (2025-09-10)

• Support Python 3.14.

• Use a different random seed per test, based on the test ID.

This change should mean that tests exercise more random data values in a given run, and that any randomly-generated identifiers have a lower chance of collision when stored in a shared resource like a database.

`PR [#687](https://github.com/pytest-dev/pytest-randomly/issues/687) https://github.com/pytest-dev/pytest-randomly/issues/687`*. Thanks to Bryce Drennan for the suggestion in `Issue [#600](https://github.com/pytest-dev/pytest-randomly/issues/600) https://github.com/pytest-dev/pytest-randomly/issues/600`* and initial implementation in `PR [#617](https://github.com/pytest-dev/pytest-randomly/issues/617) https://github.com/pytest-dev/pytest-randomly/pull/617`__.

• Move from MD5 to CRC32 for hashing test IDs, as it’s 5x faster and we don’t need cryptographic security.

`Issue [#686](https://github.com/pytest-dev/pytest-randomly/issues/686) https://github.com/pytest-dev/pytest-randomly/issues/686`__.

Commits • `50de096` Version 4.0.1 • `f9406ec` Modify Numpy seed restriction (#691) • `22049aa` Remove the random state caching (#690) • `ded2e54` Version 4.0.0 • `cb9b861` Move from MD5 to CRC32 for hashing test IDs (#688) • `bd697bd` Use a different random seed per test (#687) • `acadf46` Generate default seed on demand (#685) • `f818056` Support Python 3.14 (#684) • `456f787` Drop unused import of xdist • `e00b782` [pre-commit.ci] pre-commit autoupdate (#682) • Additional commits viewable in compare view [Dependabot compatibility score](https://camo.githubusercontent.com/2f834b491469cf96f983454caa8edf92c1e422bea4f804922eab31fe181b3ec3/68747470733a2f2f646570656e6461626f742d6261646765732e6769746875626170702e636f6d2f6261646765732f636f6d7061746962696c6974795f73636f72653f646570656e64656e63792d6e616d653d7079746573742d72616e646f6d6c79267061636b6167652d6d616e616765723d75762670726576696f75732d76657273696f6e3d332e31362e30266e65772d76657273696f6e3d342e302e31) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot show <dependency name> ignore conditions

will show all of the ignore conditions of the specified dependency •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) meltano/meltano

#9505 chore: pre-commit autoupdate Pull request opened by pre-commit-ci[bot] updates: • github.com/astral-sh/uv-pre-commit: 0.8.16 → 0.8.17 meltano/meltano

#3278 chore: pre-commit autoupdate Pull request opened by pre-commit-ci[bot] updates: • github.com/astral-sh/uv-pre-commit: 0.8.16 → 0.8.17 meltano/sdk

#9508 chore(deps): Bump the runtime-dependencies group across 1 directory with 7 updates Pull request opened by dependabot[bot] Bumps the runtime-dependencies group with 7 updates in the / directory: | Package | From | To | | -------------------------------------------------------------------- | ------- | ------- | | [azure-core](https://github.com/Azure/azure-sdk-for-python) | 1.35.0 | 1.35.1 | | [azure-identity](https://github.com/Azure/azure-sdk-for-python) | 1.24.0 | 1.25.0 | | [google-cloud-storage](https://github.com/googleapis/python-storage) | 3.3.1 | 3.4.0 | | [boto3](https://github.com/boto/boto3) | 1.40.29 | 1.40.32 | | [faker](https://github.com/joke2k/faker) | 37.6.0 | 37.8.0 | | [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | 1.1.0 | 1.1.1 | | [mypy](https://github.com/python/mypy) | 1.17.1 | 1.18.1 | Updates

azure-core

from 1.35.0 to 1.35.1 Release notes Sourced from azure-core's releases.

## azure-core_1.35.1

## 1.35.1 (2025-09-11)

### Bugs Fixed

• Fixed an issue where the

retry_backoff_max

parameter in

RetryPolicy

and

AsyncRetryPolicy

constructors was being ignored, causing retry operations to use default maximum backoff values instead of the user-specified limits. #42444

### Other Changes

•

BearerTokenCredentialPolicy

and

AsyncBearerTokenCredentialPolicy

will now properly surface credential exceptions when handling claims challenges. Previously, exceptions from credential token requests were suppressed; now they are raised and chained with the original 401

HttpResponseError

response for better debugging visibility. #42536

Commits • `e4fde9e` [Core] Prepare release (#42966) • `df01859` [Core] Read stream challenge error response (#42920) • `1a598ea` [Core] Chain challenge responses with token exceptions (#42536) • `9958caf` NOCI move tools/azure-sdk-tools under eng/tools and all references acr... • `6af5eaf` [Core] Fix ignored retry_backoff_max in RetryPolicies (#42444) • `61bb88f` Add logging section to azure-core README.md (#42391) • `4e688ad` Put obvious fake values for cred linter (#42124) • `0e64863` Increment package version after release of azure-core (#41887) • `4e048f8` [Mgmt Core] Prepare release (#41883) • See full diff in compare view Updates

azure-identity

from 1.24.0 to 1.25.0 Release notes Sourced from azure-identity's releases.

## azure-identity_1.25.0

## 1.25.0 (2025-09-11)

### Features Added

•

AzureDeveloperCliCredential

now supports

claims

in

get_token

and

get_token_info

. (#42568)

• Added new keyword argument

require_envvar

to

DefaultAzureCredential

to enforce the presence of the

AZURE_TOKEN_CREDENTIALS

environment variable. (#42660)

### Bugs Fixed

• Fixed an issue where

AzureDeveloperCliCredential

would time out during token requests when

azd

prompts for user interaction. This issue commonly occurred in environments where the

AZD_DEBUG

environment variable was set, causing the Azure Developer CLI to display additional prompts that interfered with automated token acquisition. (#42535)

• Fixed an issue where credentials configured with a default tenant ID of "organizations" (such as

InteractiveBrowserCredential

and

DeviceCodeCredential

) would fail authentication when a specific tenant ID was provided in

get_token

or

get_token_info

method calls. (#42721)

### Other Changes

• Updated

SharedTokenCacheCredential

to raise

CredentialUnavailableError

instead of

ClientAuthenticationError

during token refresh failures when within the context of

DefaultAzureCredential

. (#42934)

Commits • `0da8698` Make Prepare-Release.ps1 executable (#42976) • `2352685` Increment package version after release of azure-core (#42979) • `2dac85a` updated CHANGELOG.md with the release information 4.14.0b4 (2025-09-11) (#42972) • `fcc40eb` Mypy Dev Requirement Installation Fix (#42973) • `eb0ecce` [Identity] Adjust cache credential error behavior in DAC (#42934) • `95c0373` Add custom instructions to fetch TypeSpec docs (#42970) • `e150a42` Fix getting secret keys for connections of type "Custom Keys" (#42937) • `f6ac36d` Session Token Manual Override Fix (#42965) • `e4fde9e` [Core] Prepare release (<https://redirect.github.com/Azure/azure-sdk-for-python/issues… meltano/meltano

#3280 feat: Select streams for testing Pull request opened by edgarrmondragon ## Summary • Added comprehensive tests for the new

streams

parameter in

TapTestRunner

• Fixed existing factory tests to accommodate the new parameter ## Test Coverage Added • TapTestRunner initialization with streams parameter (list, tuple, empty, None) • run_sync_dry_run method with streams parameter • Integration test for complete workflow with streams • Compatibility with other initialization arguments ## Changes Made • tests/core/testing/test_runners.py: Added 7 new test methods for streams parameter • tests/core/testing/test_factory.py: Updated 3 existing tests to include

streams=None

parameter ## Test Plan • All new tests pass • All existing tests in test_runners.py pass (38 tests total) • All existing tests in test_factory.py pass (23 tests total) • No breaking changes to existing functionality 🤖 Generated with Claude Code ## Summary by Sourcery Introduce a 'streams' parameter to TapTestRunner and propagate it through the testing factory and runner, extend run_sync_dry_run to filter streams by name or object, and add comprehensive tests for streams behavior. New Features: • Support passing a 'streams' parameter to TapTestRunner to limit which streams are processed during dry-run execution • Expose the 'streams' parameter in testing factory functions new_test_class and get_tap_test_class Enhancements: • Extend TapBase.run_sync_dry_run to accept stream names or objects and select them correctly before running the dry run Tests: • Add unit tests for TapTestRunner initialization with streams as list, tuple, empty sequence, and None • Add tests for run_sync_dry_run with and without streams parameter and with other kwargs • Add an integration-style test covering a full TapTestRunner workflow using the streams parameter • Update existing test_factory tests to include the new streams argument meltano/sdk

#9509 chore(deps): Bump the runtime-dependencies group across 1 directory with 9 updates Pull request opened by dependabot[bot] Bumps the runtime-dependencies group with 9 updates in the / directory: | Package | From | To | | ------------------------------------------------------------------------- | ------- | ------- | | [check-jsonschema](https://github.com/python-jsonschema/check-jsonschema) | 0.33.3 | 0.34.0 | | [psutil](https://github.com/giampaolo/psutil) | 7.0.0 | 7.1.0 | | [uv](https://github.com/astral-sh/uv) | 0.8.17 | 0.8.18 | | [azure-core](https://github.com/Azure/azure-sdk-for-python) | 1.35.0 | 1.35.1 | | [azure-identity](https://github.com/Azure/azure-sdk-for-python) | 1.24.0 | 1.25.0 | | [google-cloud-storage](https://github.com/googleapis/python-storage) | 3.3.1 | 3.4.0 | | [boto3](https://github.com/boto/boto3) | 1.40.29 | 1.40.33 | | [faker](https://github.com/joke2k/faker) | 37.6.0 | 37.8.0 | | [mypy](https://github.com/python/mypy) | 1.17.1 | 1.18.1 | Updates

check-jsonschema

from 0.33.3 to 0.34.0 Release notes Sourced from check-jsonschema's releases.

## 0.34.0

• Update vendored schemas: bitbucket-pipelines, buildkite, compose-spec, dependabot, drone-ci, github-issue-forms, gitlab-ci, meltano, mergify, renovate, snapcraft, woodpecker-ci (2025-09-17)

• Add GitHub issue config schema and pre-commit hook. Thanks `@​vivodi`! (#589)

• Add GitHub issue form schema and pre-commit hook. Thanks `@​vivodi`! (#588)

• Add Codecov config schema and pre-commit hook. Thanks `@​vivodi`! (#598)

Changelog Sourced from check-jsonschema's changelog.

## 0.34.0

• Update vendored schemas: bitbucket-pipelines, buildkite, compose-spec, dependabot, drone-ci, github-issue-forms, gitlab-ci, meltano, mergify, renovate, snapcraft, woodpecker-ci (2025-09-17)

• Add GitHub issue config schema and pre-commit hook. Thanks user`vivodi`! (issue`589`)

• Add GitHub issue form schema and pre-commit hook. Thanks user`vivodi`! (issue`588`)

• Add Codecov config schema and pre-commit hook. Thanks user`vivodi`! (pr`598`)

Commits • `2d21e3d` Bump version for release • `e75ba21` Merge pull request #598 from vivodi/codecov • `cf898d3` Merge branch 'main' into codecov • `c8cc508` Merge pull request #602 from sirosen/update-changelog • `cc55c75` Fix missing step in RTD build • `daa4441` Tweak changelog to add thanks lines • `300b843` Merge pull request #601 from python-jsonschema/use-dependency-groups • `c2dc75c` Switch from development extras to dependency-groups • `e0505d1` Merge pull request #599 from python-jsonschema/vendor-schemas-auto • `323aed1` [vendor-schemas] automated update • Additional commits viewable in compare view Updates

psutil

from 7.0.0 to 7.1.0 Changelog Sourced from psutil's changelog.

# 7.1.0

2025-09-17

Enhancements

• 2581_, [Windows]: publish ARM64 wheels. (patch by Matthieu Darbois)

• 2571_, [FreeBSD]: Dropped support for FreeBSD 8 and earlier. FreeBSD 8 was maintained from 2009 to 2013.

• 2575_: introduced

dprint

CLI tool to format .yml and .md files.

Bug fixes

• 2473_, [macOS]: Fix build issue on macOS 11 and lower.

• 2494_, [Windows]: All APIs dealing with paths, such as`Process.memory_maps()`_, `Process.exe()`_ and `Process.open_files()`_ does not properly handle UNC paths. Paths such as

\\??\\C:\\Windows\\Temp

and`'\\Device\\HarddiskVolume1\\Windows\\Temp'` are now converted to`C:\\Windows\\Temp`. (patch by Ben Peddell)

• 2506_, [Windows]: Windows service APIs had issues with unicode services using special characters in their name.

• 2514_, [Linux]: `Process.cwd()`_ sometimes fail with

FileNotFoundError

due to a race condition.

• 2526_, [Linux]: `Process.create_time()`_, which is used to univocally identify a process over time, is subject to system clock updates, and as such can lead to `Process.isrunning()`_ returning a wrong result. A monotonic creation time is now used instead. (patch by Jonathan Kohler)

• 2528_, [Linux]: `Process.children()`_ may raise

PermissionError

. It will now raise `AccessDenied`_ instead.

• 2540_, [macOS]: `boot_time()`_ is off by 45 seconds (C precision issue).

• 2541_, 2570_, 2578_ [Linux], [macOS], [NetBSD]: `Process.create_time()`_ does not reflect system clock updates.

• 2542_: if system clock is updated `Process.children()`_ and`Process.parent()`_ may not be able to return the right information.

• 2545_: [Illumos]: Fix handling of MIB2_UDP_ENTRY in `net_connections()`_.

• 2552_, [Windows]: `boot_time()`_ didn't take into account the time spent during suspend / hibernation.

• 2560_, [Linux]: `Process.memory_maps()`_ may crash with

IndexError

on RISCV64 due to a malformed

/proc/{PID}/smaps

file. (patch by Julien Stephan)

• 2586_, [macOS], [CRITICAL]: fixed different places in C code which can trigger a segfault.

• 2604_, [Linux]: `virtual_memory()`_ "used" memory does not match recent versions of

free

CLI utility. (patch by Isaac K. Ko)

• 2605_, [Linux]:

psutil.sensors_battery()

reports a negative amount for seconds left.

• 2607_, [Windows]:

WindowsService.description()

method may fail with`ERROR_NOT_FOUND`. Now it returns an empty string instead.

• 2610:, [macOS], [CRITICAL]: fix `cpu_freq()`_ segfault on ARM architectures.

... (truncated) Commits • `0d18187` Revert HISTORY notes about #2629. We still do publish 3.6 and 3.7 wheels. • `229e2de` Pre-release • <https://github.com/giampaolo/psutil/commit/fb75b28226ec8e6b9e5b9eefa05a62de… meltano/meltano

#9511 ci: Stabilize integration tests by setting `UV_EXCLUDE_NEWER` Pull request opened by edgarrmondragon ## Description ## Related Issues • Closes #XXXX ## Summary by Sourcery Improve error handling in plugin invocation to distinguish missing executables from other file access errors, augment tests accordingly, and stabilize integration tests by setting UV_EXCLUDE_NEWER in CI Bug Fixes: • Differentiate between missing executables and other file access errors when catching FileNotFoundError in plugin invocation by only raising ExecutableNotFoundError for the former Enhancements: • Refine UnknownCommandError test assertions and import necessary types in plugin invoker tests CI: • Set FORCE_COLOR and UV_EXCLUDE_NEWER in integration tests workflow to stabilize CI Tests: • Add tests for ExecutableNotFoundError behavior and class message formatting • Add tests to ensure FileNotFoundError is propagated for non-executable file access issues meltano/meltano

#9510 fix: Nuanced error detection for `FileNotFoundError` in plugin execution Pull request opened by edgarrmondragon ## Description ## Related Issues • Closes #XXXX ## Summary by Sourcery Handle FileNotFoundError more precisely during plugin execution by introducing ExecutableNotFoundError for missing executables and preserving original errors for other file access failures, with corresponding test coverage enhancements New Features: • Introduce ExecutableNotFoundError to explicitly represent missing plugin executables • Differentiate between missing executables and plugin file access errors by inspecting FileNotFoundError.filename Enhancements: • Update the invocation pipeline to raise ExecutableNotFoundError only when the executable path itself is absent and rethrow other file errors unchanged • Refactor test_unknown_command to assert on the exception instance and its command attribute Tests: • Add async tests for missing executable and missing plugin file scenarios • Add direct tests to verify ExecutableNotFoundError messaging and usage meltano/meltano

#9489 feat: add `env` field to job definitions [DRAFT] Pull request opened by cjohnhanson on <!date^1757342962^{date_short}|2025-09-08T14:49:22Z> ## Summary Implements the data model and CLI interface for job environment variables as requested in #6386. This PR adds the ability to define environment variables on jobs but does not yet propagate them during job execution. ## Changes • Add

env

field to TaskSets model (

dict[str, str]

) • Support YAML dict format:

{tasks: [...], env: {KEY: value}}

• Add CLI parameters:

--env KEY=value

for

job add

and

job set

• Job listing includes environment variables in output • Full backward compatibility with existing job definitions • Comprehensive test coverage following existing patterns ## TODO (before marking ready) • Environment variable propagation during

meltano run job-name

• Environment variable precedence order during execution ## Example Usage

yaml  
jobs:

• name: gitlab  
tasks: [dbt-postgres:seed, tap-gitlab, target-postgres]  
env:  
DBT_MODELS: +gitlab+  
TARGET_BATCH_SIZE: "100"

bash  
meltano job add my-job --tasks "tap-github target-jsonl" --env DBT_MODELS=+models+ --env BATCH_SIZE=100

Related to #6386 ## Summary by Sourcery Introduce support for environment variables on jobs by extending the TaskSets model, YAML parsing, and CLI commands to accept and display env vars while preserving backward compatibility. New Features: • Allow defining environment variables on jobs via the YAML

env

field • Add

--env KEY=value

option to

job add

and

job set

commands Enhancements: • Extend TaskSets to include an

env

attribute and merge CLI-provided vars with YAML • Update job listing (text and JSON) to include environment variables • Enhance tasks_from_yaml_str to parse and validate

env

entries in dict format • Modify TaskSetsService update logic to fully replace jobs (including env) for correct persistence Tests: • Add CLI tests for adding, setting, and listing jobs with environment variables • Add core tests for parsing and validating

env

in TaskSets • Add service tests to verify storage and retrieval of job env vars meltano/meltano

#9504 feat: make PluginInvoker use manifest for env var resolution Pull request opened by cjohnhanson on <!date^1757954097^{date_short}|2025-09-15T16:34:57Z> ## Summary Updates PluginInvoker to read environment variables from the compiled manifest instead of expanding them at runtime. This is the first step toward using the manifest as the single source of truth for configuration (#7271). ## Changes • Add

src/meltano/core/manifest/loader.py

with functions to load/compile manifests • Update

PluginInvoker.env()

to check manifest first, fall back to original logic if unavailable • Auto-compile manifest when missing (same behavior as

meltano compile

) • Log warning when manifest is stale (meltano.yml newer than manifest) ## Context The manifest already contains all resolved environment variables after compilation. Reading from it directly avoids the complex runtime expansion logic in PluginInvoker. Without this change, env var resolution happens every time a plugin is invoked, requiring multiple passes of variable expansion. With this change, we read pre-resolved values from the manifest when available. ## Notes • Fully backwards compatible - falls back to original behavior if manifest unavailable • Auto-compilation might be unexpected during

meltano invoke

, but follows the pattern of other Meltano commands • One test required

project_function

fixture instead of

project

due to class-scoped isolation ## Test plan • Added 13 unit tests for manifest loader • Added 4 tests for PluginInvoker manifest integration • Created integration test for end-to-end validation • Verified no regressions in existing tests • Pre-commit hooks pass Fixes #7271 ## Summary by Sourcery Use the compiled Meltano manifest as the primary source for resolving environment variables in PluginInvoker, with lazy loading, auto-compilation of missing or stale manifests, and fallback to existing expansion logic when needed. New Features: • Introduce a manifest loader module that locates, loads, checks staleness, and compiles project manifests • Update PluginInvoker.env to fetch pre-resolved environment variables from the compiled manifest, auto-compiling the manifest if it’s missing Enhancements: • Log warnings when the manifest is stale or a plugin is not found in the manifest • Implement lazy loading of manifest data in PluginInvoker and graceful fallback to legacy env var expansion CI: • Add a new "meltano-invoker-manifest" integration test job to the GitHub Actions workflow Documentation: • Provide an example library with documentation and scripts illustrating PluginInvoker manifest usage Tests: • Add 13 unit tests for the manifest loader and 4 integration tests for PluginInvoker manifest support • Include an end-to-end integration test example project demonstrating manifest-based env resolution meltano/meltano