Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump go-github to v62 + fixes #2304

Merged
merged 14 commits into from
Jul 3, 2024

Conversation

EttoreFoti
Copy link
Contributor

This is updating the core go-github package from v57 to v62 and adjusting all the resources impacted to be backwards compatible.
This is also fixing tests that were previously broken, covering most of the resources, this would be a new activity to plan IMHO.


Before the change?

  • go-github@v57

After the change?

  • go-github@v62

Pull request checklist

  • [X ] Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • [ X] No

@EttoreFoti EttoreFoti mentioned this pull request Jul 1, 2024
4 tasks
Copy link
Member

@kfcampbell kfcampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your effort here! I'm looking forward to getting this in.

github/resource_github_branch_protection_v3_utils.go Outdated Show resolved Hide resolved
@@ -82,6 +82,56 @@ func resourceGithubRelease() *schema.Resource {
Type: schema.TypeString,
Computed: true,
},
"release_id": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How come this additional schema is added in this PR? Shouldn't there be a corresponding docs change for this as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are already in the docs as attribute reference, they were missing from the schema I guess because it was allowed in older tf sdk versions but as of today the resource is breaking and this is fixing it. The attributes are all computed and so only attribute reference, not parameters.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh got it, thanks!

github/resource_github_repository_webhook.go Outdated Show resolved Hide resolved
Copy link
Member

@kfcampbell kfcampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awesome, thank you for updating!

@kfcampbell kfcampbell merged commit d3784bd into integrations:main Jul 3, 2024
3 checks passed
@EttoreFoti EttoreFoti deleted the f-bump_go_github_v62 branch July 3, 2024 20:18
@kfcampbell kfcampbell mentioned this pull request Jul 3, 2024
1 task
kireque referenced this pull request in kireque/home-ops Jul 9, 2024
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [github](https://registry.terraform.io/providers/integrations/github)
([source](https://togithub.com/integrations/terraform-provider-github))
| required_provider | patch | `6.2.2` -> `6.2.3` |

---

### Release Notes

<details>
<summary>integrations/terraform-provider-github (github)</summary>

###
[`v6.2.3`](https://togithub.com/integrations/terraform-provider-github/releases/tag/v6.2.3)

[Compare
Source](https://togithub.com/integrations/terraform-provider-github/compare/v6.2.2...v6.2.3)

<!-- Release notes generated using configuration in .github/release.yml
at main -->

#### What's Changed

##### 🛠️ Maintenance

- build(deps): bump the github-actions group with 2 updates by
[@&#8203;dependabot](https://togithub.com/dependabot) in
[https://github.com/integrations/terraform-provider-github/pull/2303](https://togithub.com/integrations/terraform-provider-github/pull/2303)

##### 🏷 Other Changes

- fix: Fixing `enterprise_id` import on
`github_enterprise_actions_permissions` by
[@&#8203;ErikElkins](https://togithub.com/ErikElkins) in
[https://github.com/integrations/terraform-provider-github/pull/2274](https://togithub.com/integrations/terraform-provider-github/pull/2274)
- Bump go-github to v62 + fixes by
[@&#8203;EttoreFoti](https://togithub.com/EttoreFoti) in
[https://github.com/integrations/terraform-provider-github/pull/2304](https://togithub.com/integrations/terraform-provider-github/pull/2304)
- docs: mark enterprise runner visibility required by
[@&#8203;gustavlasko](https://togithub.com/gustavlasko) in
[https://github.com/integrations/terraform-provider-github/pull/2278](https://togithub.com/integrations/terraform-provider-github/pull/2278)

#### New Contributors

- [@&#8203;gustavlasko](https://togithub.com/gustavlasko) made their
first contribution in
[https://github.com/integrations/terraform-provider-github/pull/2278](https://togithub.com/integrations/terraform-provider-github/pull/2278)

**Full Changelog**:
integrations/terraform-provider-github@v6.2.2...v6.2.3

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://togithub.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjYuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyNi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS90ZXJyYWZvcm0iLCJ0eXBlL3BhdGNoIl19-->

Co-authored-by: kireque-bot[bot] <143391978+kireque-bot[bot]@users.noreply.github.com>
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