Skip to content

New version: Teradata.Loom version 1.3.0#406201

Merged
microsoft-github-policy-service[bot] merged 1 commit into
microsoft:masterfrom
ilsiepotamus:teradata-loom-1.3.0
Jul 23, 2026
Merged

New version: Teradata.Loom version 1.3.0#406201
microsoft-github-policy-service[bot] merged 1 commit into
microsoft:masterfrom
ilsiepotamus:teradata-loom-1.3.0

Conversation

@ilsiepotamus

@ilsiepotamus ilsiepotamus commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Updates Teradata.Loom to version 1.3.0

Changes

  • Update to v1.3.0
  • Update SHA256 hashes for both installers

Verification

Automated PR from GitHub Actions.

@microsoft-github-policy-service agree

Microsoft Reviewers: Open in CodeFlow

@wingetbot

Copy link
Copy Markdown
Collaborator

Validation Pipeline Run WinGetSvc-Validation-148-406201-20260722-1

ilsiepotamus added a commit to teradata-labs/loom that referenced this pull request Jul 22, 2026
wingetcreate has rejected the CLI invocation on every run since January
2026, and its exit 1 marked every winget publish as failed even when
the manual fallback then submitted the PR successfully (it merged 1.0.2
and opened microsoft/winget-pkgs#406201 for 1.3.0). The manifest-
template path is now the only path, so run status reflects reality.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@wingetbot wingetbot added New-Manifest Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed labels Jul 22, 2026
@microsoft-github-policy-service
microsoft-github-policy-service Bot enabled auto-merge (squash) July 23, 2026 00:15
@stephengillie stephengillie added the Moderator-Approved One of the Moderators has reviewed and approved this PR label Jul 23, 2026
@microsoft-github-policy-service
microsoft-github-policy-service Bot merged commit 873172e into microsoft:master Jul 23, 2026
1 check passed
ilsiepotamus added a commit to teradata-labs/loom that referenced this pull request Jul 23, 2026
….0.1 (#272)

* ci(release): fix Homebrew tap publishing that silently broke after v1.0.1

The tap (teradata-labs/homebrew-tap) was stuck at v1.0.1 while
v1.0.2-v1.3.0 shipped. Two independent breaks:

1. publish-homebrew.yml and publish-winget.yml trigger on
   `release: published`, but release.yml publishes releases with
   GITHUB_TOKEN, and GitHub suppresses workflow triggers for events
   created by GITHUB_TOKEN. The publishers never ran automatically.
   Fix: new publish-packages job in release.yml dispatches both
   publishers via workflow_dispatch (exempt from the suppression)
   after all release assets exist. Prerelease tags are skipped.

2. Even when run manually, publish-homebrew.yml only opened a PR on
   the tap, and the tap's ruleset requires an approving review no bot
   PR ever gets - all six v1.0.2 PRs were closed unmerged. Fix: merge
   the PR in-workflow with `gh pr merge --admin` (the tap ruleset now
   has a Repository admin bypass entry), failing loudly if rejected.

Documents the publish chain, token/ruleset requirements, and manual
recovery in docs/reference/release-packaging.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci(release): recompute loom-patterns resource hash on Homebrew publish

homebrew-tap#9 (takeover of community PR #7) moved pattern installation
into a checksummed Homebrew resource block pinned to the source tag
tarball. The publish workflow now hashes that tarball too and rewrites
all three sha256 values per formula, with a post-edit verification step
that fails the run if any expected hash is missing. Dead URL seds
removed: formula URLs derive from v#{version} since homebrew-tap#9.

Also corrects the stale test-count claim in CLAUDE.md (3,851 test
functions across 424 files, verified by grep).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* docs(release): winget publisher requires workflow scope on the PAT

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci(winget): remove the never-working wingetcreate path

wingetcreate has rejected the CLI invocation on every run since January
2026, and its exit 1 marked every winget publish as failed even when
the manual fallback then submitted the PR successfully (it merged 1.0.2
and opened microsoft/winget-pkgs#406201 for 1.3.0). The manifest-
template path is now the only path, so run status reflects reality.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* docs(readme): graph memory context budget default is 20%, not 10%

DefaultGraphMemoryConfig() sets ContextBudgetPercent: 20
(pkg/agent/config_loader.go) and the loader test asserts it; the
README claimed 10%, which is only a preset-template value. Example
YAML updated to show the actual default.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
@wingetbot

Copy link
Copy Markdown
Collaborator

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

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

Labels

Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Moderator-Approved One of the Moderators has reviewed and approved this PR New-Manifest Publish-Pipeline-Succeeded Validation-Completed Validation passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants