Nodestream

Latest version: v0.14.3

Safety actively analyzes 715032 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 15

0.12.5a11

What's Changed
* Actually file format support by zprobst in https://github.com/nodestream-proj/nodestream/pull/337


**Full Changelog**: https://github.com/nodestream-proj/nodestream/compare/0.12.5a10...0.12.5a11

0.12.5a10

What's Changed
* Minor Fix to Local Credential Logic by zprobst in https://github.com/nodestream-proj/nodestream/pull/336


**Full Changelog**: https://github.com/nodestream-proj/nodestream/compare/0.12.5a9...0.12.5a10

0.12.5a9

What's Changed
* AWS Credentials Refresh when Not Assuming Roles by zprobst in https://github.com/nodestream-proj/nodestream/pull/335


**Full Changelog**: https://github.com/nodestream-proj/nodestream/compare/0.12.5.a8...0.12.5a9

0.12.5.a8

What's Changed
* Interpreter Schema Generation v2 by angelosantos4 in https://github.com/nodestream-proj/nodestream/pull/333


**Full Changelog**:

- Pre-initialization check for schema correctness given `VALIDATE_PIPELINE_SCHEMA` environment variable is set. This schema introspection fix assumes that there is only one source node to be interpreted under any ingest. A check is made for the following:
- Interpreter: Only one of the before iteration phase or interpretations phase can generate source nodes.
- MultipleInterpretationPass: If one of the passes contains a source node, all of the other passes must contain a source node.
- InterpretationPass: Only one of the interpretations can assign a source node.
- SwitchInterpretations: If one of the branches contains a source node, all of the other passes including the default branch must contain a source node.
- For GraphQL schema generation, LocalDateTime objects are now DateTime objects.

- The before iteration interpretations are now accounted for within the schema introspection. (We acknowledge that either the before iteration and interpretation phases can act as source node creators.)
- Introspection is now broken down into context levels for each component that expands schema from children. For example:
1. Each pipeline has their own isolated context level.
2. For a Multiple Interpretation pass, each interpretation pass has their own context level that is distinct but inherits data from the interpreter (i.e if there is a before iteration phase with relationships).
3. For a switch interpretation, each {key: interpretations}, has their own context, ONLY if it is a source node generator. otherwise, each pass is added to the overall interpreter context.


- The switch interpretation now represents the interpretations for each key as an interpretation pass.
- Source node creators are now added to the end of the schema generation process.

0.12.5a7

What's Changed
* Cardinality Overrides by angelosantos4 in https://github.com/nodestream-proj/nodestream/pull/330
* Fix S3 Extractor object_format by grantleehoffman in https://github.com/nodestream-proj/nodestream/pull/331
* Create pre-release by grantleehoffman in https://github.com/nodestream-proj/nodestream/pull/332


**Full Changelog**: https://github.com/nodestream-proj/nodestream/compare/0.12.5a6...0.12.5a7

0.12.5a6

What's Changed
* DynamoDB Extractor by angelosantos4 in https://github.com/nodestream-proj/nodestream/pull/323
* fix message deletion by grantleehoffman in https://github.com/nodestream-proj/nodestream/pull/328
* Bump pre-release version by grantleehoffman in https://github.com/nodestream-proj/nodestream/pull/329


**Full Changelog**: https://github.com/nodestream-proj/nodestream/compare/0.12.5a5...0.12.5a6

Page 4 of 15

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.