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

chore(release/0.15.0): release 0.15.0 #918

Conversation

aeternity-bot
Copy link
Collaborator

@aeternity-bot aeternity-bot commented Sep 9, 2024

🤖 I have created a release beep boop

0.15.0 (2024-09-11)

Features

Bug Fixes


This PR was generated with Release Please. See documentation.

Copy link

github-actions bot commented Sep 9, 2024

@janmichek
Copy link
Collaborator

@Liubov-crypto Please test this with priority.
If you find something, please post it here.
It's better more smaller posts other than one big one.

@Liubov-crypto
Copy link
Collaborator

  1. Status explanation is broken in Search results:

search

@Liubov-crypto
Copy link
Collaborator

  1. Info on the Node page is looking very huddled together:

node

@Liubov-crypto
Copy link
Collaborator

  1. Alignment on Token Details page:

ali

@Liubov-crypto
Copy link
Collaborator

  1. I've connected the wallet, but after refreshing the page connection was lost:
2024-09-09.6.23.09.mov

@Liubov-crypto
Copy link
Collaborator

  1. I was not able to verify any of these contracts:
    ct_2345SH2MLhB8U4fTfUVnyHFEptfimcunBRhCXsSunkBe5okST5
    ct_2v9i8ELMd2uBJTLjgKwzMmcKrbPiQTYpvnJWU1SKy3dSXHxrYq
    ct_2K7XXvocjH3uerTbxWxn7KECn8Z6gjn7ETYv4mwQaQ47vUrL32
2024-09-09.7.05.36.mov

ver

@janmichek
Copy link
Collaborator

  1. I was not able to verify any of these contracts:
    ct_2345SH2MLhB8U4fTfUVnyHFEptfimcunBRhCXsSunkBe5okST5
    ct_2v9i8ELMd2uBJTLjgKwzMmcKrbPiQTYpvnJWU1SKy3dSXHxrYq
    ct_2K7XXvocjH3uerTbxWxn7KECn8Z6gjn7ETYv4mwQaQ47vUrL32

2024-09-09.7.05.36.mov

ver

Looks like the contents are not identical. It has to be some white space or something.

@janmichek
Copy link
Collaborator

janmichek commented Sep 10, 2024

  1. I've connected the wallet, but after refreshing the page connection was lost:

2024-09-09.6.23.09.mov

This is known limitation #867

@Liubov-crypto

This comment was marked as outdated.

@Liubov-crypto

This comment was marked as outdated.

@Liubov-crypto
Copy link
Collaborator

Also search is becoming broken when I'm searching for the contract:

search

I have to refresh the page to see the results.

@Liubov-crypto
Copy link
Collaborator

I was able to check events emitter using this contract: ct_22GBsCYdQ7ANzGwXtQzs6fQv6CWvV8NL6Fka9XWgYr4YeJM1Zi

2024-09-10.2.12.34.mov

@janmichek
Copy link
Collaborator

Also search is becoming broken when I'm searching for the contract:

search

I have to refresh the page to see the results.

That looks like it's working for me. What ID did you paste? Can you attach a video of it?

@Liubov-crypto
Copy link
Collaborator

here is video:
https://github.com/user-attachments/assets/0c3e4077-2da3-403e-a0a2-bf441d1ac5ba

@aeternity-bot aeternity-bot force-pushed the release-please--branches--release/0.15.0--components--release-please-action branch from 9a85dbd to d376407 Compare September 11, 2024 08:13
@janmichek janmichek requested review from Liubov-crypto and removed request for Liubov-crypto September 11, 2024 08:21
Copy link
Collaborator

@Liubov-crypto Liubov-crypto left a comment

Choose a reason for hiding this comment

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

I will register an issue with smart contracts verification as a separate issue. The rest is LGTM.

@janmichek janmichek merged commit c823831 into release/0.15.0 Sep 12, 2024
3 checks passed
@janmichek janmichek deleted the release-please--branches--release/0.15.0--components--release-please-action branch September 12, 2024 07:36
@aeternity-bot
Copy link
Collaborator Author

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

Successfully merging this pull request may close these issues.

3 participants