Skip to content

update: standata latest#332

Open
VsevolodX wants to merge 1 commit into
mainfrom
chore/latest-dev
Open

update: standata latest#332
VsevolodX wants to merge 1 commit into
mainfrom
chore/latest-dev

Conversation

@VsevolodX

@VsevolodX VsevolodX commented Jun 15, 2026

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • Chores
    • Updated package dependency configuration to remove version pinning for mat3ra-standata, allowing flexible version installation across multiple notebook examples.

@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

In config.yml, the mat3ra-standata package is unpinned from version ==2026.5.15.post0 in the packages_pyodide list of both the specific_examples and api_examples notebook sections, leaving it without an explicit version constraint.

Changes

Unpin mat3ra-standata

Layer / File(s) Summary
Remove version pin for mat3ra-standata
config.yml
mat3ra-standata==2026.5.15.post0 is replaced with mat3ra-standata (no version constraint) under packages_pyodide in both the specific_examples and api_examples notebook sections.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 A version pin once held so tight,
Two lines changed, the package set free tonight.
standata roams without its chain,
In pyodide lists, it hops again.
Latest release, the bunny's delight! 🌟

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'update: standata latest' clearly summarizes the main change: removing version pinning from mat3ra-standata to allow latest versions.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/latest-dev

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@config.yml`:
- Line 54: The mat3ra-standata package at line 54 is fully unpinned, which
prevents the installer from treating it as versioned and causes it to not be
reinstalled when profile changes occur, potentially leaving stale versions in
existing sessions. Replace the unpinned mat3ra-standata entry with a bounded
version specification such as mat3ra-standata>=2026.5.15.post0 to ensure it
remains eligible for version-specifier-based reinstall paths while still
allowing upgrades. Apply the same change to the mat3ra-standata reference at
line 76 to maintain consistency.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0b99e524-8acd-4196-9f84-8892252757c2

📥 Commits

Reviewing files that changed from the base of the PR and between a3a4ec2 and bf9f263.

📒 Files selected for processing (1)
  • config.yml

Comment thread config.yml
- name: specific_examples
packages_pyodide:
- mat3ra-standata==2026.5.15.post0
- mat3ra-standata

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Read-only verification:
# 1) confirm both unpinned entries in config
# 2) confirm reinstall gate depends on version operators

rg -n 'mat3ra-standata' config.yml
rg -n 'def package_has_version_specifier|def should_reinstall_package|VERSION_SPECIFIERS' src/py/mat3ra/notebooks_utils/pyodide/packages/install.py -n -A4 -B2

Repository: Exabyte-io/api-examples

Length of output: 791


Unpinning here can freeze stale versions in existing sessions and weaken reproducibility.

With mat3ra-standata fully unpinned (lines 54, 76), the installer's should_reinstall_package() gate no longer treats it as versioned, so profile changes won't force uninstall/reinstall for this package. Combined with hash-by-spec-string, this can leave older installed versions in long-lived environments even after newer releases exist.

Consider using a bounded spec like mat3ra-standata>=2026.5.15.post0 so it remains eligible for the version-specifier reinstall path while still allowing upgrades.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@config.yml` at line 54, The mat3ra-standata package at line 54 is fully
unpinned, which prevents the installer from treating it as versioned and causes
it to not be reinstalled when profile changes occur, potentially leaving stale
versions in existing sessions. Replace the unpinned mat3ra-standata entry with a
bounded version specification such as mat3ra-standata>=2026.5.15.post0 to ensure
it remains eligible for version-specifier-based reinstall paths while still
allowing upgrades. Apply the same change to the mat3ra-standata reference at
line 76 to maintain consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant