Skip to content

Debug library - #12

Merged
oskaresparza merged 3 commits into
developmentfrom
debug_library
Aug 12, 2026
Merged

Debug library#12
oskaresparza merged 3 commits into
developmentfrom
debug_library

Conversation

@oskaresparza

Copy link
Copy Markdown
Collaborator

No description provided.

oskaresparza and others added 3 commits August 12, 2026 07:55
- .github/dependabot.yml: weekly PRs for pip (pyproject.toml) and
  github-actions (workflow pin) ecosystem updates.
- .github/workflows/security.yml: CodeQL static analysis for Python
  plus pip-audit against the installed dependency set, on push to
  development/staging/main, on every PR, weekly, and on demand.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
actions/checkout@v4 and actions/setup-python@v5 only support Node 20,
which GitHub is deprecating on Actions runners — bump to @v5/@v6
across ci.yml, release.yml, and security.yml so they run on Node 24
natively instead of the runner's forced-compatibility shim.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Both now raise NotImplementedError immediately instead of running
their CTAS/CREATE OR REPLACE VIEW statements — signatures unchanged
so Catalog.draft2version/publishversion, _OPERATIONS dispatch, and
retry_pending all still resolve, they just fail loudly when called.

Switched the generic retry-mechanism tests that happened to use these
two as convenient examples over to deleteview/datacopy instead, and
updated README's usage example and operation list to stop advertising
them as working.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@oskaresparza
oskaresparza merged commit 6ea5a03 into development Aug 12, 2026
6 checks passed
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

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.

2 participants