Closed cbaker6 closed 2 years ago
@mtrezza it looks like the credentials have been changed for CocoaPods (see comments above), can you or someone or the Core Team update the credentials along with the required token so new versions can be pushed?
Yes, I assume this repo needs a new trunk token that is generated with the service user. Let me look into this.
Does the repo code itself contain any CocoaPods user reference?
Note to myself: same has to be done for ObjC SDK repo.
@cbaker6 I updated the trunk token, can you please try.
Note: The update was also for Parse ObjC SDK.
Does the repo code itself contain any CocoaPods user reference?
Yes, this repo produces pods here (linked to the pod badge on the readme): https://cocoapods.org/pods/ParseSwift. Previous pods pushed can be seen here: https://github.com/CocoaPods/Specs/tree/master/Specs/f/a/8/ParseSwift
Note: The update was also for Parse ObjC SDK.
I believe if you set this at the organization level of GitHub any repo that needs pods can use it. Previously we had the Swift, Objective-C, and the Objective-C LiveQuery repos sharing the same token so it stays fresh.
I updated the trunk token, can you please try.
This worked and the new pod is pushed, thanks!
New Issue Checklist
Issue Description
It looks like someone changed the CocoaPods credentials recently but didn't update the settings across the repo. The CI reports the following issue when attempting to push a new version to CocoaPods:
Steps to reproduce
Try to push a new release to cocoapods
Actual Outcome
Can't create release
Expected Outcome
To release as it was before
Environment
GitHub actions release.yml
Client
Server
Database
Logs