generated from ubiquity/ts-template
-
Notifications
You must be signed in to change notification settings - Fork 20
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
build: development to main #21
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* feat: encode decode functions for permit payloads * chore: encode decode functions for permit payloads * chore: changed username to be user id * chore: wallet upsert for users * chore: change prototype overload for permit generation * chore: fixed tests for erc721 * chore: removed useless + in string * chore: permit type checks for encode decode * chore: changed permit type checks * chore: removed unexported types * chore: removed unnecessary ignoreDependencies directive for Knip * chore: changed erc721 type to enforce 0 or 1 value * v1.0.2 * fix!: changed back userId to username * chore: renamed SUPABASE_ANON_KEY to SUPABASE_KEY * chore: excluded Numberish in cspell
return data to kernel
* feat: encode decode functions for permit payloads * chore: encode decode functions for permit payloads * chore: changed username to be user id * chore: wallet upsert for users * chore: change prototype overload for permit generation * chore: fixed tests for erc721 * chore: removed useless + in string * chore: permit type checks for encode decode * chore: changed permit type checks * chore: removed unexported types * chore: removed unnecessary ignoreDependencies directive for Knip * chore: changed erc721 type to enforce 0 or 1 value * v1.0.2 * fix!: changed back userId to username * chore: renamed SUPABASE_ANON_KEY to SUPABASE_KEY * chore: excluded Numberish in cspell * v1.0.3 * v1.1.0 * v1.1.1 * v1.2.0 * feat!: split bundling to avoid importing Node.js modules everywhere * chore: changed username to be user id * fix!: changed back userId to username * chore: removed unused package * chore: add path separators to .gitignore --------- Co-authored-by: Korrrba <gitcoiner@gmail.com>
* chore: changed esm to cjs and remove preserve modules * v1.2.1 * chore: moved code generation to dist folder * chore: bump package.json version
fix!: naming convention
Co-authored-by: Mentlegen <9807008+gentlementlegen@users.noreply.github.com>
feat: add custom reward token to permit
JUnit
Coverage Report (63%)
|
gentlementlegen
approved these changes
Jun 18, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rndquu Correct, I thought this was the most sensible way to update the package by merging into the production branch. Good to go
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@gentlementlegen As far as I understand when we merge to the
main
branch the package version is bumped and published to npm.