Skip to content

Commit

Permalink
Merge tag 'v0.80.7' of github.com:penumbra-zone/penumbra into noot/ib…
Browse files Browse the repository at this point in the history
…c-height-hack-v0.80.7

Penumbra version 0.80.7
  • Loading branch information
noot committed Oct 25, 2024
2 parents 1607f78 + 35f9f2f commit 2915670
Show file tree
Hide file tree
Showing 159 changed files with 17,648 additions and 1,034 deletions.
30 changes: 30 additions & 0 deletions .github/ISSUE_TEMPLATE/point_release.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
name: Point release
about: Checklist for preparing a point release for tooling
title: Release vX.Y.Z, via point-release
labels: ''
assignees: ''
---

# Tooling Release

<!--
Explain the rationale for this release: did a particular bugfix land that we want to ship quickly?
Is an external consumer blocked on a new RPC?
-->
In order to ship some minor improvements and bug fixes, let's prepare a `vX.Y.Z.` release, flushing out the current contents of the main branch.

## Changes to include
<!--
Explain the rationale for this release: did a particular bugfix land that we want to ship quickly?
Is an external consumer blocked on a new RPC?
-->

- [ ] Everything on current main
- [ ] Feature foo in PR:
- [ ] Feature bar in PR:

## Compatibility
As this is a point-release, all changes must be fully compatible for all nodes and clients.
Careful attention should be given to the delta between most recent tag on the main branch:
https://github.com/penumbra-zone/penumbra/compare/v(X.Y.(Z-1)..main
46 changes: 0 additions & 46 deletions .github/ISSUE_TEMPLATE/release_testnet.md

This file was deleted.

7 changes: 7 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,16 @@
## Describe your changes

<!--
Describe what's changed and why. If interactive testing is required, explain
to the reviewer how the PR should be tested.
-->

## Issue ticket number and link

## Checklist before requesting a review

- [ ] I have added guiding text to explain how a reviewer should test these changes.

- [ ] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

> REPLACE THIS TEXT WITH RATIONALE (CAN BE BRIEF)
34 changes: 31 additions & 3 deletions .github/workflows/smoke.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,13 @@ on:
paths-ignore:
- 'docs/**'

concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true

jobs:
smoke_test:
runs-on: buildjet-16vcpu-ubuntu-2204
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
environment: smoke-test
steps:
- uses: actions/checkout@v4
Expand Down Expand Up @@ -39,3 +40,30 @@ jobs:
- name: Display smoke-test logs
if: always()
run: cat deployments/logs/smoke-*.log

pmonitor-integration:
runs-on: buildjet-16vcpu-ubuntu-2204
steps:
- uses: actions/checkout@v4
with:
lfs: true

- name: install nix
uses: nixbuild/nix-quick-install-action@v28

- name: setup nix cache
uses: nix-community/cache-nix-action@v5
with:
primary-key: nix-${{ runner.os }}-${{ hashFiles('**/*.nix') }}
restore-prefixes-first-match: nix-${{ runner.os }}-
backend: buildjet

- name: Load rust cache
uses: astriaorg/[email protected]

# Confirm that the nix devshell is buildable and runs at all.
- name: validate nix env
run: nix develop --command echo hello

- name: run the pmonitor integration tests
run: nix develop --command just test-pmonitor
Loading

0 comments on commit 2915670

Please sign in to comment.