From 53a480ad7ba1e751278feac0b171d017c5383319 Mon Sep 17 00:00:00 2001 From: michelle-aptos <120680608+michelle-aptos@users.noreply.github.com> Date: Mon, 15 May 2023 08:06:34 -0400 Subject: [PATCH 1/2] Update staking.md update maximum amount --- developer-docs-site/docs/concepts/staking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer-docs-site/docs/concepts/staking.md b/developer-docs-site/docs/concepts/staking.md index 36fcb801652ac..412d6f08735a4 100644 --- a/developer-docs-site/docs/concepts/staking.md +++ b/developer-docs-site/docs/concepts/staking.md @@ -179,7 +179,7 @@ For step-by-step instructions on how to join the validator set, see: [Joining Va ### Minimum and maximum stake -You must stake the required minimum amount to join the validator set. Moreover, you can only stake up to the maximum stake amount. The current required minimum for staking is 1M APT tokens. +You must stake the required minimum amount to join the validator set. Moreover, you can only stake up to the maximum stake amount. The current required minimum for staking is 1M APT tokens and the maximum is 50M APT tokens. If at any time after joining the validator set, your current staked amount exceeds the maximum allowed stake (for example as the rewards are added to your staked amount), then your voting power and the rewards will be calculated only using the maximum allowed stake amount, and not your current staked amount. From 32a59035f8876f7a179c3abc2b12bc0662dff6b2 Mon Sep 17 00:00:00 2001 From: Stelian Ionescu Date: Mon, 22 May 2023 15:52:12 -0400 Subject: [PATCH 2/2] Require permission check before running determine-docker-build-metadata --- .github/workflows/docker-build-test.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/docker-build-test.yaml b/.github/workflows/docker-build-test.yaml index 382c0a6259a23..59fcbe294101a 100644 --- a/.github/workflows/docker-build-test.yaml +++ b/.github/workflows/docker-build-test.yaml @@ -92,13 +92,13 @@ jobs: # Because the docker build happens in a reusable workflow, have a separate job that collects the right metadata # for the subsequent docker builds. Reusable workflows do not currently have the "env" context: https://github.com/orgs/community/discussions/26671 determine-docker-build-metadata: + needs: [permission-check] runs-on: ubuntu-latest steps: - name: collect metadata run: | - echo "GIT_SHA: ${{ env.GIT_SHA }}" - echo "TARGET_CACHE_ID: ${{ env.TARGET_CACHE_ID }}" - echo "CONCURRENCY: ${{ github.workflow }}-${{ github.event_name }}-${{ (github.event_name == 'push' || github.event_name == 'workflow_dispatch') && github.sha || github.head_ref || github.ref }}" + echo "GIT_SHA: ${GIT_SHA}" + echo "TARGET_CACHE_ID: ${TARGET_CACHE_ID}" outputs: gitSha: ${{ env.GIT_SHA }} targetCacheId: ${{ env.TARGET_CACHE_ID }}