chore: update parameters in issue-label-assign (#198)

I am trying to coerce the workflow to label `aws-cdk` more than
`@aws-cdk/cli-lib-alpha` since it's far more likely that any issue that
comes in is for the cdk cli.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

chore: update parameters in issue-label-assign (#198)

I am trying to coerce the workflow to label `aws-cdk` more than
`@aws-cdk/cli-lib-alpha` since it's far more likely that any issue that
comes in is for the cdk cli.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

chore: update parameters in issue-label-assign (#198)

I am trying to coerce the workflow to label `aws-cdk` more than
`@aws-cdk/cli-lib-alpha` since it's far more likely that any issue that
comes in is for the cdk cli.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

chore: update parameters in issue-label-assign (#198)

I am trying to coerce the workflow to label `aws-cdk` more than
`@aws-cdk/cli-lib-alpha` since it's far more likely that any issue that
comes in is for the cdk cli.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

chore: update parameters in issue-label-assign (#198)

I am trying to coerce the workflow to label `aws-cdk` more than
`@aws-cdk/cli-lib-alpha` since it's far more likely that any issue that
comes in is for the cdk cli.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

chore: update parameters in issue-label-assign (#198)

I am trying to coerce the workflow to label `aws-cdk` more than
`@aws-cdk/cli-lib-alpha` since it's far more likely that any issue that
comes in is for the cdk cli.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

chore: update SDK range to `^3` (#171)

We've already moved ;)

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>

chore: update SDK range to `^3` (#171)

We've already moved ;)

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>

chore: update SDK range to `^3` (#171)

We've already moved ;)

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>

chore: update SDK range to `^3` (#171)

We've already moved ;)

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

---------

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>