feat: new REQUIREMENTS_FILEPATH for lambda-python wf#77
Merged
Conversation
rbapst-tamedia
approved these changes
Nov 26, 2025
DCamma
approved these changes
Dec 1, 2025
tamedia-fission Bot
pushed a commit
that referenced
this pull request
Dec 9, 2025
## [3.15.0](v3.14.0...v3.15.0) (2025-12-09) ### ✨ Features * new REQUIREMENTS_FILEPATH for lambda-python wf ([#77](#77)) ([667d44a](667d44a))
|
🎉 This PR is included in version 3.15.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adding an option to use a requirements.txt file in a different path other than source_dir.
Motivation and Context
A single requirements.txt doesn't always "fits-all", some projects have shared resources and smaller scripts and fewer requirements.
This change allows a small script to have it's own dependencies instead of relies on root's requirements.txt.
Breaking Changes
None
How Has This Been Tested?
.github/workflows/_test-*.yamlto demonstrate and validate my change(s)pre-commit run -aon my pull requestmake gen_docs_runon my pull requestGithub Conventional Commit Release
https://dnd-it.github.io/github-workflows/workflows/gh-release/