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

GH pages release works, but the ci job exits with non 0 #292

Closed
BelfordZ opened this issue May 23, 2020 · 1 comment · Fixed by #293
Closed

GH pages release works, but the ci job exits with non 0 #292

BelfordZ opened this issue May 23, 2020 · 1 comment · Fixed by #293

Comments

@BelfordZ
Copy link
Member

No description provided.

BelfordZ added a commit that referenced this issue May 23, 2020
@BelfordZ BelfordZ changed the title GH pages release not working anymore GH pages release works, but the ci job exits with non 0 Jun 12, 2020
BelfordZ pushed a commit that referenced this issue Feb 1, 2023
# [1.3.0](1.2.6...1.3.0) (2023-02-01)

### Bug Fixes

* bump node version and update circle config ([52403aa](52403aa))
* dont point to latest json schema  ([114202c](114202c)), closes [#330](#330)
* follow conventional capitalization pattern ([bb3b838](bb3b838))
* markdown inside html doenst work ([664eec1](664eec1))
* missing bracket  ([8f6e649](8f6e649))
* re-order release perparation steps ([4893ac8](4893ac8)), closes [#292](#292)
* remove example object referencing content descriptor use ([b9f00de](b9f00de)), closes [/github.com//issues/315#issuecomment-718258896](https://github.com//github.com/open-rpc/spec/issues/315/issues/issuecomment-718258896)
* s/supercedes/supersedes/ ([91533e3](91533e3))
* shamelessly add funding link via open collective ([c3f8de2](c3f8de2))
* typo in Example Object ([c551b21](c551b21))
* update discord link ([d75ceeb](d75ceeb))
* update labler to v4 ([cd3ac52](cd3ac52))

### Features

* add support for strict notification methods ([a9a3091](a9a3091)), closes [#230](#230)
@BelfordZ
Copy link
Member Author

BelfordZ commented Feb 1, 2023

🎉 This issue has been resolved in version 1.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant