FilOzone / FilOzone/pdp-explorer
Release v1.1.0
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 7
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 4
Description
## Release Checklist
> [!IMPORTANT]
> Follow the canonical [Subgraph Release Process](https://github.com/FilOzone/pdp-explorer/blob/main/docs/subgraph/release.md). This issue records the status of this release; the runbook defines the process and commands.
### 1. Confirm the release
- [x] The Release Please PR for `v1.1.0` was merged
- [x] The `v1.1.0` tag and GitHub Release were created
- [x] The `Deploy subgraph to Goldsky (calibration)` job succeeded
- [x] The `Deploy subgraph to Goldsky (mainnet)` job succeeded
### 2. Await subgraph indexing
- [ ] Received confirmation that `pdp-explorer-mainnet/1.1.0` has finished indexing
- [ ] Received confirmation that `pdp-explorer-calibration/1.1.0` has finished indexing
### 3. Verify the candidate
- [ ] Explorer loads without errors on mainnet
- [ ] Explorer loads without errors on calibration
- [ ] Changes included in this release were smoke-tested
### 4. Promote the subgraphs to `prod`
- [ ] `pdp-explorer-mainnet/1.1.0` is tagged as `prod`
- [ ] `pdp-explorer-calibration/1.1.0` is tagged as `prod`
### 5. Verify production
- [ ] [PDP Explorer](https://pdp.filecoin.cloud) loads and functions correctly on mainnet after the tag switch
- [ ] [PDP Explorer](https://pdp.filecoin.cloud) loads and functions correctly on calibration after the tag switch
- [ ] Dependent clients using the `prod` endpoints load and function correctly
### 6. Wrap up
- [ ] The release was announced to the appropriate channel
- [ ] Any improvements needed in the release process were documented
- [ ] Close this issue
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with docs/subgraph/release.md, the canonical Subgraph Release Process, and use this issue's checklist to track the v1.1.0 release. Verify indexing, candidate and production behavior for mainnet and calibration, promote both subgraphs to prod, announce the release, document process improvements, and close the issue when every applicable check is complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100