Skip to content

fix: using correct token to publish #15

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 4, 2023
Merged

fix: using correct token to publish #15

merged 1 commit into from
May 4, 2023

Conversation

xShteff
Copy link
Member

@xShteff xShteff commented May 4, 2023

No description provided.

@xShteff xShteff requested a review from a team as a code owner May 4, 2023 11:35
mbogh
mbogh approved these changes May 4, 2023
View reviewed changes
Copy link
Collaborator

@mbogh mbogh left a comment

Choose a reason for hiding this comment

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

🗝️

@xShteff xShteff merged commit 7f0a4dd into main May 4, 2023
@xShteff xShteff deleted the fix/token branch May 4, 2023 11:37
mobile-platform-buddy bot pushed a commit that referenced this pull request May 4, 2023
@semantic-release-bot
chore(release): 1.1.0 [skip ci]
3d768ae 
# [1.1.0](v1.0.0...v1.1.0) (2023-05-04)

### Bug Fixes

* using correct token to publish ([#15](#15)) ([7f0a4dd](7f0a4dd))

### Features

* now publishing to npmjs  ([#14](#14)) ([5249612](5249612))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mbogh mbogh mbogh approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@xShteff @mbogh