Skip to content

chore: resolve dependency update conflicts - #189

Merged
francoischalifour merged 3 commits into
altertable-ai:dependabot/bun/development-dependencies-c1d909ef58from
albert20260301:chore/resolve-pr-187-conflict
Sep 1, 2026
Merged

francoischalifour merged 3 commits into
altertable-ai:dependabot/bun/development-dependencies-c1d909ef58from
albert20260301:chore/resolve-pr-187-conflict

Conversation

@albert20260301

Copy link
Copy Markdown
Contributor

Summary

Impact

This stacked PR updates only the conflicted Dependabot branch. Once merged, PR #187 becomes mergeable without changing its dependency-update scope.

Validation

  • bun install --frozen-lockfile (Bun 1.4.0)
  • bun run lint
  • bun run test (467 passing)

dependabot Bot and others added 3 commits September 1, 2026 11:43
…ai#188)

Bumps
[@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)
from 24.10.1 to 26.4.0.
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@types/node&package-manager=bun&previous-version=24.10.1&new-version=26.4.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
## Summary

- pin every third-party GitHub Action in the semantic-title, release,
test, and integration workflows to its reviewed commit SHA
- move Linux jobs to `ubuntu-24.04`
- retain the repository's `.node-version` and `.bun-version` runtime
contracts

## Impact

This is workflow-only hardening. It does not change the SDK packages,
release contract, or runtime behavior. The existing community-file PR
altertable-ai#180 modifies a separate legacy semantic-workflow path; it remains
unsafe to merge because it would add a duplicate noncompliant check.

## Verification

- `bash /root/.openclaw/workspace/scripts/validate-workflow-policy.sh
/root/.openclaw/workspace/code/altertable-js`
- `git diff --check`
- YAML parse for all modified workflows
- `bun run lint`
- `bun run test`
@albert20260301

Copy link
Copy Markdown
Contributor Author

@francoischalifour This stacked PR resolves #187 after #188 and #186 advanced main. It preserves both dependency update sets; lint and 467 unit tests pass locally. Please merge #189, then #187 will be clean for its existing approvals.

@francoischalifour
francoischalifour merged commit 10026ee into altertable-ai:dependabot/bun/development-dependencies-c1d909ef58 Sep 1, 2026
2 checks passed
@albert20260301
albert20260301 deleted the chore/resolve-pr-187-conflict branch September 1, 2026 11:22
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