Skip to content

chore(main): release 0.7.1 - #65

Merged
nicknisi merged 1 commit into
mainfrom
release-please--branches--main--components--workos
Feb 18, 2026
Merged

chore(main): release 0.7.1#65
nicknisi merged 1 commit into
mainfrom
release-please--branches--main--components--workos

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

0.7.1 (2026-02-18)

Bug Fixes

  • ground AI analysis in SDK documentation (#64) (db8d6e3)

This PR was generated with Release Please. See documentation.

@nicknisi
nicknisi merged commit e2e4865 into mainFeb 18, 2026
2 checks passed
@nicknisi
nicknisi deleted the release-please--branches--main--components--workos branch February 18, 2026 21:15
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Created releases:

🌻

lucasmotta added a commit that referenced this pull request Feb 20, 2026
…ts-skills
* origin/main: (21 commits)
chore(main): release 0.7.2 (#67)
fix: Correct issue submission links (#66)
chore(main): release 0.7.1 (#65)
fix: ground AI analysis in SDK documentation (#64)
chore(main): release 0.7.0 (#60)
fix: improve installer skill and remove shell: true from spawn calls (#63)
feat: major workos doctor overhaul — visual refresh, multi-language, AI analysis (#62)
fix: replace dotenv devDependency with inline env parser in doctor (#61)
feat: add environment, organization, and user management commands (#59)
chore(main): release 0.6.0 (#58)
feat: agent self-correction via validation feedback loop (#57)
chore(main): release 0.5.4 (#56)
fix: restore workflow_call and remove registry-url for OIDC
chore(main): release 0.5.3 (#55)
fix: trigger release.yml directly via release event for OIDC match
fix: remove registry-url from setup-node to unblock OIDC auth
chore(main): release 0.5.2 (#54)
fix: use npm publish for OIDC trusted publishing support
chore(main): release 0.5.1 (#53)
fix: remove duplicate release trigger causing publish race condition
...
# Conflicts:
#	src/lib/adapters/cli-adapter.ts
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant

@nicknisi