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

feat: ML challenge launch copy updates #1318

Merged
merged 14 commits into from
Nov 6, 2024

Conversation

kne42
Copy link
Member

@kne42 kne42 commented Nov 6, 2024

@kne42 kne42 merged commit 7ceff67 into main Nov 6, 2024
7 checks passed
@kne42 kne42 deleted the kira/ml-challenge-launch-copy-updates branch November 6, 2024 18:43
github-actions bot added a commit that referenced this pull request Nov 6, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.36.0](web-v1.35.1...web-v1.36.0)
(2024-11-06)


### ✨ Features

* challenge status banner
([#1319](#1319))
([1bd0bff](1bd0bff))
* definition and search updates
([#1298](#1298))
([58e36ea](58e36ea))
* ML challenge launch copy updates
([#1318](#1318))
([7ceff67](7ceff67))
* order datasets by release date
([#1320](#1320))
([788c178](788c178))
* universal empty states
([#1295](#1295))
([ef64faa](ef64faa))


### 🐞 Bug Fixes

* download code snippets
([#1315](#1315))
([b137eb4](b137eb4))
* fix single run page view tomogram button
([#1325](#1325))
([da6902c](da6902c))
* fix view tomogram button greyed out error
([#1323](#1323))
([5a6ca7a](5a6ca7a))
* table hover state
([#1300](#1300))
([800ad33](800ad33))


### 🧹 Miscellaneous Chores

* fix ml challenge page nits
([#1324](#1324))
([9ba9fa7](9ba9fa7))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants