Skip to content

chore(main): release 1.0.0 - #26

Open
source-release-bot[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--source-coop-cli
Open

source-release-bot[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--source-coop-cli

Conversation

@source-release-bot

@source-release-bot source-release-bot Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.0.0 (2026-11-09)

⚠ BREAKING CHANGES

  • existing cached logins are no longer found; run source-coop login once after upgrading.

Features

  • account commands: list, view and edit accounts, create organizations (#97) (a4e92c8)
  • api: -q for query parameters, one typed -f, and -F for a body file (#56) (b4a8274)
  • auth commands: login, status, logout and token under auth (#46) (f31ae44)
  • cache non-production credentials per proxy host so staging and prod coexist (#22) (8673032)
  • dates show as RFC 3339 plus a relative time everywhere (#55) (8bc6e2d)
  • docs: publish the guide as a versioned site with PR previews (#76) (80a2561)
  • manage members and invitations (member, invitation) (#57) (fc59ce9)
  • one login session for STS and the source.coop API (#23) (d55e4b7)
  • picker: show that / filters what's loaded and Enter searches the server (#61) (909f771)
  • product commands: list, view, create, edit and delete, with -i (#47) (528d627)
  • product edit offers the visibilities its data connection allows (#54) (032dd90)
  • product view and list give the data's S3 path (s3_uri, s3_endpoint) (#103) (12a6b16)
  • product: edit opens a form of current values instead of asking which fields to change (#62) (84e4aea)
  • read the API's RFC 9457 problems (#67) (504c486)
  • send a source-coop-cli User-Agent to source.coop (#87) (f9151ca)
  • service-account commands for service accounts, their sign-ins and product access (#58) (bc95481)
  • shared foundation for API-backed commands, and the api command (#45) (a0db3e6)
  • shell completion for commands, flags and ACCOUNT/PRODUCT names (#63) (476b1b0)

Bug Fixes

  • complete: wait for the keychain password dialog instead of exiting mid-dialog (#65) (f2e265e)
  • demo: answer errors as problems, invite as "invited", read without changing (#72) (7d95e1d)
  • demo: keep demos off the real login, and wait on the right text (#71) (e082efb)
  • docs: remove a closed PR's preview (#79) (3f0e7b3)
  • member: use the /memberships resource that replaced the member endpoints (#66) (5e44cc6)
  • product: an editor that won't open no longer ends the edit form (#64) (5ee6c37)
  • product: offer the data connections the API says an account may use (#53) (fd8ea66)
  • product: recognise a product membership by product_id (#52) (abb444a)

This PR was generated with Release Please. See documentation.

@source-release-bot
source-release-bot Bot force-pushed the release-please--branches--main--components--source-coop-cli branch from 3740670 to fc2dda2 Compare October 13, 2026 17:30
@source-release-bot source-release-bot Bot changed the title chore(main): release 0.4.0 chore(main): release 1.0.0 Oct 13, 2026
@source-release-bot
source-release-bot Bot force-pushed the release-please--branches--main--components--source-coop-cli branch 15 times, most recently from 814a7c1 to 72618b7 Compare October 19, 2026 19:50
@source-release-bot
source-release-bot Bot force-pushed the release-please--branches--main--components--source-coop-cli branch 2 times, most recently from a55d60a to ffa4cd4 Compare October 27, 2026 05:46
@source-release-bot
source-release-bot Bot force-pushed the release-please--branches--main--components--source-coop-cli branch from ffa4cd4 to 62fb1da Compare November 4, 2026 19:40
@alukach
alukach requested a review from tylere November 5, 2026 20:21
@source-release-bot
source-release-bot Bot force-pushed the release-please--branches--main--components--source-coop-cli branch 8 times, most recently from 8a216c2 to 54193b6 Compare November 9, 2026 05:19
@source-release-bot
source-release-bot Bot force-pushed the release-please--branches--main--components--source-coop-cli branch from 54193b6 to 0961963 Compare November 9, 2026 19:11
@tylere

tylere commented Nov 18, 2026

Copy link
Copy Markdown

I tried to recreate something similar to the Source Coop CLI + AI - 1: Create Product demo. I was surprised to see that the agent created a private GH repo, but a public Source.Coop product. By default, I would expect that the agent would either:

  1. prompt me for input on important privacy choices, or
  2. default to conservative, private choices

Modifying agents.md might address this.

Claude's response when I asked about this behavior:

 Why did you decide to make the GitHub repo private, and the source coop product public?

You didn't specify either one, and I picked both without asking. I should have flagged them.

- Repo private: I treated it as the cautious default for a new repo on your account. Private keeps it out of public view until you decide otherwise, and OIDC works the same either way.
- Product public: I copied --visibility public from the CLI's help example rather than choosing it on purpose. My guess was that a public test product on staging was harmless and easy to look at in the browser.

Put side by side, that's inconsistent. Anyone can see the data, but not the tooling that writes it. For a throwaway staging test, either choice is fine. If you want them to match:
- Repo public: gh repo edit tylere/source-coop-datetime-heartbeat --visibility public --accept-visibility-change-consequences
- Product private: source-coop-next-staging product edit tylere/datetime-heartbeat --visibility restricted (or unlisted). The DEV connection allows both.

@tylere

tylere commented Nov 18, 2026

Copy link
Copy Markdown

The CLI docs instruct me to check the version, but it is not clear what I gain by knowing the version. The selector only shows "next" and "latest", neither of which are version numbers

image

Run source-coop --version to see yours.

tylere@Tylers-MacBook-Pro-3 source_cli_testing % source-coop --version
source-coop 0.2.0

@tylere

tylere commented Nov 18, 2026

Copy link
Copy Markdown

https://cli.source.coop/next/

image

What does "are stable" mean in this context?

@tylere

tylere commented Nov 18, 2026

Copy link
Copy Markdown

Suggest consolidating on either demo-org or my-org rather than using both.

image

@tylere

tylere commented Nov 18, 2026 •

Copy link
Copy Markdown

https://cli.source.coop/latest/install/ describes how to install using Homebrew, but the cask is not found.

tylere@Tylers-MacBook-Pro-3 source_cli_testing % brew info source-cooperative/tap/source-coop
Error: No available formula or cask with the name "source-cooperative/tap/source-coop".
This command requires the tap source-cooperative/tap.
If you trust this tap, tap it explicitly and then try again:
  brew tap source-cooperative/tap

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant