Skip to content

chore(deps): bump rust-toolchain from 1.98.0 to 1.98.1 - #494

Draft
dependabot[bot] wants to merge 9 commits into
mainfrom
dependabot/rust_toolchain/rust-toolchain-1.98.1
Draft

chore(deps): bump rust-toolchain from 1.98.0 to 1.98.1#494
dependabot[bot] wants to merge 9 commits into
mainfrom
dependabot/rust_toolchain/rust-toolchain-1.98.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 9, 2026

Copy link
Copy Markdown
Contributor

Rust 1.98.1 compatibility repair

Rust 1.98.1 was published by the Rust Release Team on 2026-09-03 to fix a rustc vtable-generation miscompilation present in 1.98.0. This Draft keeps the Dependabot patch update and repairs verified repository-level consequences without changing the declared MSRV or weakening CI/security policy.

Current exact head is 97e10a646ca43babcf06c6e36d5bd8f6b1c3b16a on protected main@a243f18da4a4ca8a8d068c39922537f1f8ed6ad0.

Preserved RED → repair lineage

Original Dependabot head c8acfcfe68fd1f65b62d9f345ad5920adbe3515f changed only rust-toolchain.toml from 1.98.0 to 1.98.1. Subsequent forward commits synchronized repository contract tests, stable CI lanes, the commercial verifier and current schedule-admission expectations while preserving Cargo.toml rust-version = "1.98.0" as MSRV and keeping repository-local scheduling removed.

Official compiler source: Rust Release Team. (2026, September 3). Announcing Rust 1.98.1. Rust Blog. https://blog.rust-lang.org/2026/09/03/Rust-1.98.1/

Remaining code-current source finding

ARCHITECTURE.md still states: “Stable Rust 1.98.0 is the compile, lint, test, and line-coverage reference.” The branch's root toolchain/CI/verifier build reference is 1.98.1, so that sentence still requires a one-line repair before this PR is code-current.

An attempted narrow edit at 54ed1dcc6d59cf696763a999a5553ba423ddc372 was rejected by exact diff review because it unintentionally omitted three existing architecture-table rows while changing the intended sentence. The omission was immediately repaired by ordinary forward commit 97e10a646ca43babcf06c6e36d5bd8f6b1c3b16a. Comparing ea2e5ec... to 97e10a... yields no file delta, so the branch is source-equivalent to the last verified source head; the stale architecture sentence therefore remains unresolved rather than being claimed fixed. No force update or destructive rebase was used.

Do not globally replace every 1.98.0 occurrence. Cargo.toml rust-version = "1.98.0" remains the MSRV and historical ADR/CHANGELOG evidence remains historical truth. Dockerfile still uses the verified immutable 1.98.0 Bookworm image; do not substitute an unverified 1.98.1 tag or digest.

The repository-local commercial entrypoint also still contains legacy provider-key/bootstrap behavior owned by #492 / .github#2038 / contextual-orchestrator #1023/#1083. This compiler patch must not copy or redesign that unpublished orchestration contract.

Exact-head verification

Fresh exact-head workflows for 97e10a646ca43babcf06c6e36d5bd8f6b1c3b16a are terminal:

  • Documentation Quality 34564877786: GREEN.
  • Rust Foundation 34564877774: GREEN.
  • Security Scan 34564877776: GREEN.
  • SAST Semgrep 34564877798: GREEN.
  • CodeQL PR 34564877779: RED in the delegated compatibility receipt path.

CodeQL language detection job 103154836880 and fresh current-head dispatch job 103157070548 are GREEN. Compatibility jobs 103155462817 (python) and 103155462854 (actions) both read the current-head dispatch verdict successfully and then fail at Release runner or enforce current-head CodeQL verdict. This is the same delegated producer/handler settlement class already owned centrally; it is not evidence of a Rust 1.98.1 compiler/source regression and is not a reason to weaken or bypass CodeQL.

The canonical central owner remains .github#1929 with combined successor .github#2040. On .github#2040@6706c231ab06a3c91c43fdb5b989cfcd79fff593, Security Scan, SAST Semgrep, Python Security, and Agent Review Runtime Quality are terminal GREEN while CodeQL PR 34251822255 is terminal RED; attempt 7 fails in the central actions/python verdict path and current-head dispatch. TEPP must not synthesize a receipt, loop no-op consumer pushes, or fork that control-plane repair locally.

Review / merge bar

The only formal review remains the historical OpenCode CHANGES_REQUESTED submission on original head c8acfcfe...; it is not a qualifying current-head approval. There are no unresolved inline review threads. This PR remains Draft and unmerged.

Before Ready/merge: repair only the stale ARCHITECTURE.md build-reference sentence without changing MSRV/history/Docker provenance; acquire a terminal GREEN CodeQL receipt through the canonical owner path; and obtain a qualifying independent current-head approval. No force push, destructive rebase, self-approval, fabricated receipt, unverified image substitution, gate weakening, no-op rerun loop, or routine admin bypass.

Bumps [rust-toolchain](https://github.com/rust-lang/rust) from 1.98.0 to 1.98.1.
- [Release notes](https://github.com/rust-lang/rust/releases)
- [Changelog](https://github.com/rust-lang/rust/blob/main/RELEASES.md)
- [Commits](rust-lang/rust@1.98.0...1.98.1)

---
updated-dependencies:
- dependency-name: rust-toolchain
  dependency-version: 1.98.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust_toolchain_package_manager Pull requests that update rust_toolchain_package_manager code labels Sep 9, 2026

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for c8acfcfe68fd1f65b62d9f345ad5920adbe3515f.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Repository file: rust-toolchain.toml"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Repository file: rust-toolchain.toml"]
  R1 --> V1["required checks"]
Loading

@opencode-agent

opencode-agent Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

@seonghobae
seonghobae marked this pull request as draft September 10, 2026 18:02

Copy link
Copy Markdown
Contributor

현재 exact head ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45를 다시 확인해 Draft로 되돌렸습니다. 이 head에서 Rust Foundation, Documentation Quality, Security Scan, SAST Semgrep은 GREEN이지만 CodeQL PR 34321064222는 terminal FAILURE이고 qualifying current-head APPROVE도 없습니다. 또한 PR 자체가 ARCHITECTURE.md의 “Stable Rust 1.98.0 … reference” 문구를 code-current finding으로 남기고 있습니다. 따라서 Ready 상태는 실제 acceptance와 맞지 않았습니다.

이 전환은 source/history를 버리거나 gate를 약화하는 조치가 아닙니다. 기존 Rust 1.98.1 toolchain/CI/scheduler repair delta는 그대로 보존합니다. 다음 owner-correct repair는 (1) 1.98.1은 build-reference pin, Cargo.toml rust-version = 1.98.0은 MSRV라는 구분을 ARCHITECTURE/research/ADR에서 일관되게 doctoring하고, (2) Dockerfile은 검증된 immutable 1.98.1 Bookworm image/digest가 없으면 임의 변경하지 않으며, (3) current-head CodeQL failure를 canonical .github evidence path와 분리해 RCA한 뒤 fresh exact-head checks와 independent approval을 다시 받는 것입니다. CHANGELOG의 과거 1.98.0 기록과 의도된 MSRV contract는 역사/호환성 근거이므로 단순 문자열 치환 대상이 아닙니다.

Copy link
Copy Markdown
Contributor

CodeQL RED도 current-head job 단위로 분류했습니다. Run 34321064222에서 Detect CodeQL languagesDispatch current-head CodeQL scan은 GREEN입니다. 실패한 것은 actions/python compatibility job의 Release runner or enforce current-head CodeQL verdict이며, 바로 앞 Read current-head CodeQL dispatch verdict 단계는 둘 다 성공했습니다. 즉 Rust 1.98.1 source/toolchain 자체의 CodeQL 분석 finding으로 해석할 근거가 아니라, exact-head terminal verdict를 leaf compatibility gate가 수용하지 못한 control-plane/receipt 경로 RED입니다.

따라서 이 PR에서 CodeQL requirement를 제거하거나 우회하지 않습니다. Canonical .github owner가 head/language/workflow/run-bound terminal verdict publication을 정상화한 뒤 같은 ea2e5ec... 또는 실제 repair successor에서 재검증해야 합니다. Source가 움직이면 predecessor verdict는 이전하지 않습니다.

Copy link
Copy Markdown
Contributor

Fresh foundation coordination from the TEPP Validation Evidence lane: exact ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45 is still Draft/open/mergeable. Current-head Rust Foundation 34321064196, Documentation Quality 34321064193, Security Scan 34321064166, and SAST Semgrep 34321064175 are terminal GREEN; CodeQL PR 34321064222 is terminal RED, so this head is not merge evidence. The existing OpenCode CHANGES_REQUESTED submission is on the original c8acfcfe... head and is not a current-head approval.

The code-current documentation finding in this PR body is still real: ARCHITECTURE.md on this branch still says Stable Rust 1.98.0 is the compile, lint, test, and line-coverage reference, while the branch manifest/CI verifier is now 1.98.1. Please repair that wording in this toolchain-owner lane and reacquire exact-head checks rather than changing #488/#492 to mask the drift. If/when #494 lands on protected main, #492 and then stacked #488 will need ordinary non-force restack/revalidation against the new protected base; predecessor exact-head evidence must not transfer across that base/toolchain change.

Copy link
Copy Markdown
Contributor

@coderabbitai review ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45 only. Please verify the Rust 1.98.1 repository-wide compatibility delta against the exact current head, with special attention to the remaining ARCHITECTURE.md sentence that still names Rust 1.98.0 as the compile/lint/test/line-coverage reference, while Cargo.toml rust-version = "1.98.0" remains the intentional MSRV. Also check that no other current documentation/configuration incorrectly conflates the 1.98.1 build-reference pin with the 1.98.0 MSRV. Do not recommend restoring repository-local scheduling, changing provider-routing ownership, weakening CodeQL/coverage/security gates, or substituting an unverified Docker image.

@coderabbitai

coderabbitai Bot commented Sep 10, 2026

Copy link
Copy Markdown
🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '== checked-out revision =='
git rev-parse HEAD
git status --short

echo '== candidate tracked files =='
git ls-files | rg '(^|/)(ARCHITECTURE\.md|Cargo\.toml|rust-toolchain\.toml|Dockerfile|README.*|CHANGELOG.*|.*\.(md|mdx|rst|yml|yaml|json|toml))$' || true

echo '== Rust 1.98 version references in tracked text/config files =='
git grep -n -I -E '1\.98\.[01]|rust-version|rust-toolchain|toolchain install|rustup.*install' -- \
  ':**.md' ':**.mdx' ':**.rst' ':**.toml' ':**.yml' ':**.yaml' ':**.json' \
  ':Dockerfile' ':**/Dockerfile' ':Cargo.toml' ':**/Cargo.toml' ':rust-toolchain.toml' ':**/rust-toolchain.toml' || true

echo '== architecture and manifest context =='
for f in ARCHITECTURE.md Cargo.toml rust-toolchain.toml Dockerfile; do
  if [ -f "$f" ]; then
    echo "--- $f ---"
    rg -n -C 3 -I -E '1\.98\.[01]|rust-version|toolchain|Rust' "$f" || true
  fi
done

echo '== changed files at requested commit relative to first parent =='
git diff-tree --no-commit-id --name-status -r ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45^ ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45

Length of output: 19312


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '== all tracked 1.98 references with context =='
git grep -n -I -C 3 -E '1\.98\.[01]' -- ':!Cargo.lock' || true

echo '== root manifest and toolchain files =='
cat -n Cargo.toml | sed -n '116,134p'
cat -n rust-toolchain.toml
cat -n ARCHITECTURE.md | sed -n '158,176p'
cat -n docs/research/rust-quality-tooling.md | sed -n '1,105p'
cat -n docs/adr/0007-rust-workspace-quality-gates.md | sed -n '1,85p'

echo '== CI/verifier toolchain and schedule context =='
rg -n -C 5 -I 'rustup toolchain install 1\.98\.1|rust-toolchain\.toml|schedule:|workflow_dispatch|cwl-org-commercial-entrypoint' \
  .github/workflows/ci.yml .github/workflows/hourly-nim-product-development.yml

echo '== Python contract references =='
git grep -n -I -C 3 -E 'rust-version|1\.98\.[01]|rust-toolchain' -- '*.py' || true

echo '== cumulative requested-head diff from merge base with main =='
base="$(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD main)"
printf 'base=%s\n' "$base"
git diff --stat "$base"..HEAD
git diff --find-renames --unified=40 "$base"..HEAD -- \
  rust-toolchain.toml Cargo.toml ARCHITECTURE.md docs/research/rust-quality-tooling.md \
  .github/workflows/ci.yml .github/workflows/hourly-nim-product-development.yml \
  ':**.py'

Length of output: 73396


@seonghobae 검토 결과, 정확한 head ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45에서 수정이 필요한 현재성 문제는 하나입니다.

  • ARCHITECTURE.md Line 168: “Stable Rust 1.98.0 is the compile, lint, test, and line-coverage reference.”는 현재 상태와 다릅니다. 이 문장은 Rust 1.98.1을 stable build-reference pin으로 지정해야 합니다. 또한 Cargo.tomlrust-version = "1.98.0"이 의도된 MSRV임을 명시해야 합니다.

다른 현재 문서와 구성은 이 두 버전을 올바르게 구분합니다.

  • rust-toolchain.toml은 정확한 build-reference channel로 1.98.1을 지정합니다.
  • .github/workflows/ci.yml의 stable quality, coverage, Live PostgreSQL lane은 모두 1.98.1을 설치합니다.
  • .github/workflows/hourly-nim-product-development.yml의 commercial verifier도 1.98.1을 설치합니다.
  • docs/research/rust-quality-tooling.md1.98.1 build reference와 1.98.0 MSRV를 명시적으로 구분합니다.
  • workspace contract와 해당 테스트의 1.98.0은 MSRV contract를 검증하므로 변경 대상이 아닙니다.
  • CHANGELOG.md와 ADR 0007의 1.98.0은 과거 기록 또는 출처입니다.
  • Dockerfile의 검증된 immutable rust:1.98.0-bookworm@sha256:... base는 별도 컨테이너 재현성 pin입니다. 검증된 1.98.1 대체 이미지가 없으므로 변경을 권장하지 않습니다.
  • commercial entrypoint는 workflow_dispatch만 포함하고 로컬 schedule: 블록을 포함하지 않습니다.

로컬 스케줄 복원, provider-routing 변경, CodeQL·coverage·security gate 완화, 또는 검증되지 않은 Docker image 변경은 필요하지 않습니다.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Sep 10, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 74f8ee51-78d9-416a-bf31-8ec90c676d38

📥 Commits

Reviewing files that changed from the base of the PR and between a243f18 and ea2e5ec.

📒 Files selected for processing (6)
  • .github/workflows/ci.yml
  • .github/workflows/hourly-nim-product-development.yml
  • docs/research/rust-quality-tooling.md
  • rust-toolchain.toml
  • tests/quality/test_ci_coverage_diagnostics.py
  • tests/quality/test_hourly_nim_product_development.py

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

Rust 툴체인을 1.98.1로 갱신했습니다. 모든 관련 CI 작업과 시간별 제품 품질 게이트가 동일한 버전을 설치합니다. 테스트는 고정 버전과 워크플로 계약을 검증하며, 문서는 변경 근거와 검증 기준을 갱신합니다.

Changes

Rust 툴체인 정렬

Layer / File(s) Summary
툴체인 기준과 채택 근거
rust-toolchain.toml, docs/research/rust-quality-tooling.md
고정 Rust 버전을 1.98.1로 변경했습니다. 컴파일러 수정 사항, MSRV 구분, 품질 검증 기준 및 참고 문헌을 갱신했습니다.
CI 툴체인 설치
.github/workflows/ci.yml, .github/workflows/hourly-nim-product-development.yml
CI 품질, 커버리지, PostgreSQL 및 시간별 제품 품질 게이트가 Rust 1.98.1을 설치하도록 변경했습니다.
툴체인 및 워크플로 계약 검증
tests/quality/test_ci_coverage_diagnostics.py, tests/quality/test_hourly_nim_product_development.py
테스트가 고정 버전의 형식과 정확한 설치 횟수를 검증합니다. 시간별 워크플로의 중앙 진입점 토큰과 schedule 부재 검증도 추가했습니다.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: seonghobae

Merge Risk: ⚪ Minimal · up to ea2e5

This PR only bumps the pinned Rust toolchain from 1.98.1 for CI, coverage, database, and hourly product workflows, keeping the 1.98.0 MSRV unchanged, and updates tests/docs to match. No functional or data-integrity risk was identified in the changed files. The PR remains in draft due to unrelated control-plane/CodeQL receipt issues and pending documentation/approval steps called out in the PR description, not because of a defect found in this review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 2 files. (4 skipped: 4 …
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 제목은 Rust 툴체인을 1.98.0에서 1.98.1로 업데이트하는 PR의 주요 변경 사항을 정확하고 간결하게 설명합니다.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/rust_toolchain/rust-toolchain-1.98.1

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.

Copy link
Copy Markdown
Contributor

Current-head independent review has now converged on the same single repository-local code-current defect: CodeRabbit reviewed ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45 and identified only ARCHITECTURE.md line 168, which still names Rust 1.98.0 as the compile/lint/test/line-coverage reference. It also verified that the other inspected docs/config correctly distinguish build-reference 1.98.1 from intentional Cargo.toml rust-version = "1.98.0" MSRV. Do not bulk-replace historical/MSRV 1.98.0 references.

I also re-ran only the failed jobs of CodeQL PR 34321064222 without changing source or weakening the gate. Attempt 3 is now the exact-head diagnostic authority; predecessor attempt-2 failure remains historical. If the rerun reproduces the receipt/enforcement RED, keep it on the canonical central CodeQL owner path. The architecture one-line repair still belongs on this #494 toolchain-owner branch, followed by fresh exact-head checks; #492/#488 should not be changed to mask either prerequisite.

Copy link
Copy Markdown
Contributor

Fresh central-owner handoff: .github#2040 is still open/mergeable and now Ready/Proposed at exact 6706c231ab06a3c91c43fdb5b989cfcd79fff593, but its hosted generation is terminal rather than in-progress. Security Scan 34251822390, SAST Semgrep 34251822314, Python Security 34251822251, and Agent Review Runtime Quality 34251822381 are GREEN; required CodeQL PR 34251822255 is terminal RED. Its actions/python compatibility lanes fail in the exact current-head dispatch-verdict/settlement path, so the central successor itself has not yet demonstrated the receipt contract needed by this consumer. Do not loop #494 leaf reruns or synthesize a receipt from the other GREEN workflows.

The remaining TEPP-owned #494 source repair is unchanged: correct only the stale ARCHITECTURE.md build-reference sentence from 1.98.0 to the current 1.98.1 build reference while preserving Cargo.toml rust-version = "1.98.0" as MSRV and preserving historical evidence. This comment does not mutate the #494 source lane.

Copy link
Copy Markdown
Contributor

Fresh prerequisite sweep on exact ea2e5ec612b20a05f6a89bb2fc0e896ed1bc4f45:

  • The TEPP-owned source finding is unchanged: ARCHITECTURE.md still says Stable Rust 1.98.0 is the compile/lint/test/line-coverage reference, while this branch's build-reference/CI/verifier pin is 1.98.1. Repair that sentence only; Cargo.toml rust-version = "1.98.0" remains the MSRV and historical 1.98.0 evidence remains historical truth.
  • Canonical central successor .github#2040 is now Ready/open/mergeable at 6706c231ab06a3c91c43fdb5b989cfcd79fff593. Its current hosted generation is terminal: Security Scan, Semgrep, Python Security and Agent Review Runtime Quality are GREEN; CodeQL PR 34251822255 is RED. Attempt 7 fails actions/python compatibility while reading the current-head dispatch verdict, and the dispatch-current-head scan job also fails; language detection succeeds. This remains central-owner evidence, not a Rust 1.98.1 source failure and not a reason to rerun-loop or synthesize a TEPP receipt.

Keep #494 Draft until the one-line architecture drift is repaired, the central owner yields a terminal authenticated exact-head CodeQL receipt, exact-head checks are reacquired after source mutation, and a qualifying current-head approval exists. No image-tag/digest substitution is authorized without verified immutable 1.98.1 Bookworm evidence.

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

Labels

dependencies Pull requests that update a dependency file rust_toolchain_package_manager Pull requests that update rust_toolchain_package_manager code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant