Avatar for the meltano user
meltano
meltano
BlogDocsChangelog

Performance History

Latest Results

fix(core): Do not disable existing loggers when passing logging configuration to SDK-based plugins (#9858) ## Description <!-- Describe the changes introduced by this PR --> This should prevent the loss of logs coming from configured loggers in the SDK-based plugin. ## Checklist - [x] I have read the [contribution guide](https://docs.meltano.com/contribute/merge/) ### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". See the agentic coding section of the contribution guide for details: https://github.com/meltano/meltano/blob/main/CONTRIBUTING.md#agentic-coding --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the agentic coding guidelines](https://github.com/meltano/meltano/blob/main/CONTRIBUTING.md#agentic-coding) --> ## Related Issues * Closes https://github.com/meltano/meltano/pull/9506 ## Summary by Sourcery Prevent SDK-based plugin logging configuration from disabling existing Python loggers while preserving structured vs default formatter selection based on the log parser. Bug Fixes: - Ensure SDK-based plugin logging no longer disables previously configured loggers, avoiding loss of log output from existing loggers. Enhancements: - Simplify SDK logging configuration by inlining formatter selection logic and always using a non-disabling logging config helper. Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>
main
1 day ago
fix(core): Do not disable existing loggers when passing logging configuration to SDK-based plugins This should prevent the loss of logs coming from configured loggers in the SDK-based plugin. Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>
fix/do-not-disable-sdk-loggers
1 day ago
packaging(deps): Require click 8.2.0+ (#9854) ## Description <!-- Describe the changes introduced by this PR --> Bumps the minimum version of Click to [8.2.0 published on May 10, 2025](https://pypi.org/project/click/8.2.0/) ## Checklist - [ ] I have read the [contribution guide](https://docs.meltano.com/contribute/merge/) ### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". See the agentic coding section of the contribution guide for details: https://github.com/meltano/meltano/blob/main/CONTRIBUTING.md#agentic-coding --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the agentic coding guidelines](https://github.com/meltano/meltano/blob/main/CONTRIBUTING.md#agentic-coding) --> ## Related Issues * https://github.com/meltano/meltano/pull/9793 * https://github.com/meltano/meltano/pull/9796 got lost in the ether somehow 😬 ## Summary by Sourcery Build: - Increase the Click package requirement from 8.1 to 8.2 while retaining the <8.4 upper bound and exclusion of 8.2.2. Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>
main
2 days ago
packaging(deps): Require click 8.2.0+ (#9796) <!-- Please, go through these steps when you submit a PR. 1. Make sure your branch is not protected. In particular, avoid making PRs from the `main` branch of your fork. 2. Give a descriptive title to your PR. We use semantic titles, and the accepted types and scopes are listed in https://github.com/meltano/meltano/blob/main/.github/semantic.yml. A good title should look like this: ``` feat(cli): The `meltano run` command now accepts a `--timeout` option to limit the time it runs ``` 3. Provide a description of your changes. 4. Put "Closes #XXXX" in your comment to auto-close the issue that your PR fixes (if such). --> <!-- Describe the changes introduced by this PR --> - Bumps the minimum version of Click to [8.2.0 published on May 10, 2025](https://pypi.org/project/click/8.2.0/) - https://github.com/meltano/meltano/pull/9793 will let us be more aware of our mininum requirements inn the future - https://github.com/meltano/meltano/pull/9793 Build: - Increase the required Click package version to 8.2.x while keeping the upper bound and exclusion for 8.2.2. Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>
click-v8.2
2 days ago
Merge branch 'main' into feat/config-list-required-settings
mahangu:feat/config-list-required-settings
2 days ago
ci: Bump Python to 3.14.2 in CodSpeed workflow (#9853) ## Description <!-- Describe the changes introduced by this PR --> ## Checklist - [x] I have read the [contribution guide](https://docs.meltano.com/contribute/merge/) ### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". See the agentic coding section of the contribution guide for details: https://github.com/meltano/meltano/blob/main/CONTRIBUTING.md#agentic-coding --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the agentic coding guidelines](https://github.com/meltano/meltano/blob/main/CONTRIBUTING.md#agentic-coding) --> ## Related Issues * Closes #XXXX ## Summary by Sourcery CI: - Bump Python version in the CodSpeed benchmark GitHub Actions workflow from 3.13.11 to 3.14.2. Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>
main
2 days ago
ci: Bump Python to 3.14.2 in CodSpeed workflow Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>
ci/codspeed-py3142
2 days ago
test: Reduce variance in state backend benchmarks (#9770) <!-- Please, go through these steps when you submit a PR. 1. Make sure your branch is not protected. In particular, avoid making PRs from the `main` branch of your fork. 2. Give a descriptive title to your PR. We use semantic titles, and the accepted types and scopes are listed in https://github.com/meltano/meltano/blob/main/.github/semantic.yml. A good title should look like this: ``` feat(cli): The `meltano run` command now accepts a `--timeout` option to limit the time it runs ``` 3. Provide a description of your changes. 4. Put "Closes #XXXX" in your comment to auto-close the issue that your PR fixes (if such). --> ## Description <!-- Describe the changes introduced by this PR --> ## Related Issues * Closes #XXXX ## Summary by Sourcery Update state backend benchmarks to use codspeed-style benchmarking and simplify the benchmark suite. Tests: - Wrap state store update benchmarks with pytest-codspeed BenchmarkFixture instead of invoking updates directly. - Remove repeated update benchmark variants, keeping only single-update complete and partial state benchmarks. Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>
main
2 days ago

Active Branches

feat: Show required setting indicators in `meltano config list`
last run
2 days ago
#9849
CodSpeed Performance Gauge
0%
refactor: Use `Project.activate` and `Project.find` thread-safety locks directly
last run
7 days ago
#9847
CodSpeed Performance Gauge
+1%
fix(core): Handle non-unicode characters in plugin logs on Windows
last run
12 days ago
#9831
CodSpeed Performance Gauge
-13%
© 2026 CodSpeed Technology
Home Terms Privacy Docs