Bump up to 0.8.0

[yu-iskw]

No description provided.

[coderabbitai]

Walkthrough

This pull request focuses on updating the documentation and version information for the dbt-artifacts-parser package. The changes primarily involve updating the compatibility matrix in the README to reflect support for newer versions of dbt and pydantic, and finalizing the release of version 0.8.0 by removing the release candidate (rc) designation from the version number.

Changes

File	Change Summary
README.md	Updated compatibility table to show version 0.8 supports dbt 1.5-1.9 with pydantic v2
dbt_artifacts_parser/__init__.py	Updated version from "0.8.0rc1" to "0.8.0"

Possibly related PRs

• Migrate to pydantic v2 #78: Changes related to migration to pydantic v2, which aligns with the compatibility updates in this PR

Poem

🐰 Hop, hop, version update's here!
Compatibility table now crystal clear
From rc to stable, we've made our mark
dbt and pydantic dance in the park
Version 0.8.0, our rabbit's delight! 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 984af55 and f2fb8f5.

📒 Files selected for processing (2)

• README.md (1 hunks)
• dbt_artifacts_parser/__init__.py (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• dbt_artifacts_parser/init.py

🔇 Additional comments (2)

README.md (2)

Line range hint 19-23: LGTM! Clear and proactive compatibility warnings.

The warning section effectively communicates version constraints, migration guidance, and future considerations regarding pydantic compatibility.

---

26-26: LGTM! Version compatibility update is clear and well-documented.

The compatibility table update correctly reflects the extended dbt support (up to 1.9) for version 0.8.0 while maintaining the pydantic v2 requirement.

Let's verify version consistency across the codebase:

✅ Verification successful

Version 0.8.0 is consistently defined across the codebase

The version 0.8.0 is correctly set in __init__.py and the project uses dynamic versioning through flit as specified in pyproject.toml. The version information is consistent with the compatibility matrix update in the README.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version numbers across the codebase
# Expected: Version "0.8.0" should be consistent

# Check version in setup.py/pyproject.toml
echo "Checking version in package configuration..."
rg -l "version.*0\.8\.0" "setup.py|pyproject.toml"

# Check version in __init__.py
echo "Checking version in __init__.py..."
rg "__version__.*0\.8\.0" "dbt_artifacts_parser/__init__.py"

# Check for any remaining references to rc versions
echo "Checking for remaining rc references..."
rg "0\.8\.0rc[0-9]"

Length of output: 488

---

Script:

#!/bin/bash
# Let's verify the version information with more precise commands

# Check for pyproject.toml first
echo "Looking for pyproject.toml..."
fd pyproject.toml

# Check version in all Python files
echo "Checking version strings in Python files..."
rg "version.*=.*['\"]0\.8" -A 1

# Check for any remaining RC references in the entire codebase
echo "Checking for any RC references..."
rg -i "rc[0-9]|release.candidate"

# Check package metadata
echo "Checking package metadata..."
fd "setup.cfg|setup.py"

Length of output: 70207

---

Script:

#!/bin/bash
# Let's check the version information in pyproject.toml

# First, let's see the content of pyproject.toml
echo "Content of pyproject.toml:"
cat pyproject.toml

# Let's also check any version references in the package
echo -e "\nChecking version references in Python files:"
rg -g "*.py" "version.*=.*['\"]0\.8"

Length of output: 2109

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.