Skip to content

Feat/koala 4703 allow imports#1126

Open
djantzen wants to merge 5 commits intomainfrom
feat/koala-4703-allow-imports
Open

Feat/koala 4703 allow imports#1126
djantzen wants to merge 5 commits intomainfrom
feat/koala-4703-allow-imports

Conversation

@djantzen
Copy link
Copy Markdown
Contributor

@djantzen djantzen commented Apr 3, 2026

https://canvasmedical.atlassian.net/browse/KOALA-4703

Update to match reality, and remove requests library from public docs since we prefer plugins use our HTTP library.

@djantzen djantzen requested a review from a team as a code owner April 3, 2026 01:46
@djantzen djantzen requested a review from beaugunderson April 3, 2026 01:47
@aws-amplify-us-west-2
Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1126.d298pum72820gn.amplifyapp.com

Comment thread collections/_sdk/sandboxing-and-allowed-imports.md Outdated
@djantzen djantzen force-pushed the feat/koala-4703-allow-imports branch from bc64ec0 to 60ef77a Compare April 10, 2026 17:30
@djantzen djantzen force-pushed the feat/koala-4703-allow-imports branch from 60ef77a to a064908 Compare April 10, 2026 18:16
@djantzen
Copy link
Copy Markdown
Contributor Author

@rmagier1 Should I go ahead and merge this or does it need to be merged first into a documentation repo release branch?

@rmagier1
Copy link
Copy Markdown
Contributor

@rmagier1 Should I go ahead and merge this or does it need to be merged first into a documentation repo release branch?

I should be merged into a release branch once it makes it in a release. I noticed the KOALA is merged? But there is no fix version?

@djantzen
Copy link
Copy Markdown
Contributor Author

@rmagier1 Should I go ahead and merge this or does it need to be merged first into a documentation repo release branch?

I should be merged into a release branch once it makes it in a release. I noticed the KOALA is merged? But there is no fix version?

Yeah, it has no fix version. I guess that's because I had the ticket in "ready for release" instead of "merged" but I'm not positive.

@rmagier1
Copy link
Copy Markdown
Contributor

@rmagier1 Should I go ahead and merge this or does it need to be merged first into a documentation repo release branch?

I should be merged into a release branch once it makes it in a release. I noticed the KOALA is merged? But there is no fix version?

Yeah, it has no fix version. I guess that's because I had the ticket in "ready for release" instead of "merged" but I'm not positive.

What home-app PR are these changes getting into? Basically which PR increases the plugins version so these changes are a part of it?

@djantzen
Copy link
Copy Markdown
Contributor Author

@rmagier1 Should I go ahead and merge this or does it need to be merged first into a documentation repo release branch?

I should be merged into a release branch once it makes it in a release. I noticed the KOALA is merged? But there is no fix version?

Yeah, it has no fix version. I guess that's because I had the ticket in "ready for release" instead of "merged" but I'm not positive.

What home-app PR are these changes getting into? Basically which PR increases the plugins version so these changes are a part of it?

Plugins version 0.129.0, home-app release branch 1.296.0. So it's been live for a week already it seems

@rmagier1
Copy link
Copy Markdown
Contributor

@rmagier1 Should I go ahead and merge this or does it need to be merged first into a documentation repo release branch?

I should be merged into a release branch once it makes it in a release. I noticed the KOALA is merged? But there is no fix version?

Yeah, it has no fix version. I guess that's because I had the ticket in "ready for release" instead of "merged" but I'm not positive.

What home-app PR are these changes getting into? Basically which PR increases the plugins version so these changes are a part of it?

Plugins version 0.129.0, home-app release branch 1.296.0. So it's been live for a week already it seems

Oh then maybe let's just add it to mondays release so that we can make a release notes entry so people know these things are available now.

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