Update CatalogV1 data model with latest schema

[bhuvansingla]

User description

Updates the CatalogV1 data model to support the latest schema changes.

Changes

• Updated default dbt_version from 1.9.0b2 to 1.10.0a1
• Added optional invocation_started_at field to Metadata model
• Bumped package version to 0.9.1

---

PR Type

Enhancement

---

Description

• Updated CatalogV1 data model to latest schema

• Bumped dbt_version default from 1.9.0b2 to 1.10.0a1

• Added optional invocation_started_at field to Metadata

• Incremented package version to 0.9.1

---

Changes diagram

flowchart LR
  A["CatalogV1 Schema"] --> B["Update dbt_version"]
  A --> C["Add invocation_started_at field"]
  A --> D["Bump package version"]

Loading

---

Changes walkthrough 📝

	Relevant files
Configuration changes	__init__.py Package version bump                                                                          dbt_artifacts_parser/init.py Bumped package version from 0.9.0 to 0.9.1 +1/-1
Enhancement	catalog_v1.py Metadata model schema updates                                                        dbt_artifacts_parser/parsers/catalog/catalog_v1.py Updated default dbt_version from 1.9.0b2 to 1.10.0a1 Added optional invocation_started_at field to Metadata model +2/-1      catalog_v1.json JSON schema definition updates                                                      dbt_artifacts_parser/resources/catalog/catalog_v1.json Updated default dbt_version from 1.9.0b2 to 1.10.0a1 Added invocation_started_at property with string/null types +11/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[coderabbitai]

Walkthrough

This update modifies the dbt_artifacts_parser package by incrementing its version to 0.9.1 and updating the Metadata class in catalog_v1.py to include a new optional field, invocation_started_at, and changes the default dbt_version value.

Changes

File(s)	Change Summary
dbt_artifacts_parser/init.py	Updated __version__ from "0.9.0" to "0.9.1".
dbt_artifacts_parser/parsers/catalog/catalog_v1.py	Changed default dbt_version in Metadata from '1.9.0b2' to '1.10.0a1'; added invocation_started_at field.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant MetadataClass

    User->>MetadataClass: Instantiate Metadata()
    MetadataClass-->>User: Returns instance with dbt_version='1.10.0a1', invocation_started_at (optional)

Loading

Possibly related PRs

• Set __version__ to 0.8.0rc1 #128: Both PRs update the __version__ variable in the dbt_artifacts_parser/__init__.py file to reflect new version numbers.
• Bump up to 0.8.3 #156: Both PRs update the version string in the dbt_artifacts_parser/__init__.py file but do not modify any other code or logic, indicating they are related changes focused on version bumping.
• Update the parsers using dbt artifacts of dbt-core 1.9.0-rc1 #126: This PR extends the Metadata class changes introduced in Update the parsers using dbt artifacts of dbt-core 1.9.0-rc1 #126 by updating the default dbt_version and adding a new field.

Poem

The parser hops to version one-oh-nine-one,
With dbt_version set for new things to come.
A fresh field appears, for time to be tracked—
invocation_started_at has joined the pack!
The catalog grows, the code feels bright,
As rabbits code onward, deep into the night. 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Pylint (3.3.7)

dbt_artifacts_parser/__init__.py

dbt_artifacts_parser/parsers/catalog/catalog_v1.py

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Version Consistency The dbt_version default has been updated to a pre-release version (1.10.0a1). Verify this aligns with the intended schema compatibility and that downstream consumers can handle alpha versions appropriately. dbt_version: Optional[str] = '1.10.0a1' generated_at: Optional[str] = None

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Use stable version instead of alpha Using an alpha version as a default value may cause instability issues. Consider using a stable release version instead of an alpha version for production code. dbt_artifacts_parser/parsers/catalog/catalog_v1.py [18] -dbt_version: Optional[str] = '1.10.0a1' +dbt_version: Optional[str] = '1.9.0' Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly points out the potential instability of using an alpha version (1.10.0a1) as a default, which is a valid concern for production code, even if the change was intentional.	Low
Update

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

dbt_artifacts_parser/parsers/catalog/catalog_v1.py (1)

18-21: New metadata fields added correctly; consider parsing to datetime for stronger typing

The default dbt_version='1.10.0a1' and new optional invocation_started_at field align with the updated schema.
If feasible, representing generated_at and invocation_started_at as datetime (using datetime | str with Field(..., alias=..., validate_default=True) or a custom validator) would provide stronger type safety and automatic ISO-8601 parsing while remaining JSON-serialisable.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f063f85 and 3cb3751.

⛔ Files ignored due to path filters (1)

• dbt_artifacts_parser/resources/catalog/catalog_v1.json is excluded by !**/*.json

📒 Files selected for processing (2)

• dbt_artifacts_parser/__init__.py (1 hunks)
• dbt_artifacts_parser/parsers/catalog/catalog_v1.py (1 hunks)

🔇 Additional comments (1)

dbt_artifacts_parser/__init__.py (1)

21-21: Version bump looks good — double-check all distribution metadata is in sync

__version__ is now 0.9.1, but please verify that the same version is reflected in packaging artifacts (pyproject.toml, setup.cfg, release notes, CI publish workflow) to avoid mismatch during release.