Skip to content

Conversation

@eric-haibin-lin
Copy link
Collaborator

What does this PR do?

bump main branch version to v0.5.0.dev

Checklist Before Starting

  • Search for similar PRs. Paste at least one query link here: ...
  • Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
    • {modules} include fsdp, megatron, sglang, vllm, rollout, trainer, ci, training_utils, recipe, hardware, deployment, ray, worker, single_controller, misc, perf, model, algo, env, tool, ckpt, doc, data
    • If this PR involves multiple modules, separate them with , like [megatron, fsdp, doc]
    • {type} is in feat, fix, refactor, chore, test
    • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
    • Example: [BREAKING][fsdp, megatron] feat: dynamic batching

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the project's version from 0.5.0 to 0.5.0.dev. This is a standard procedure to mark the main branch as a development version after a release. The change is confined to the version file and is consistent with the PR's objective. I've reviewed the change and it appears correct.

@eric-haibin-lin eric-haibin-lin enabled auto-merge (squash) July 23, 2025 23:44
@eric-haibin-lin eric-haibin-lin merged commit d57bfb0 into volcengine:main Jul 24, 2025
4 checks passed
@eric-haibin-lin eric-haibin-lin deleted the hlin/bump-version branch July 24, 2025 03:58
yellowbee686 pushed a commit to yellowbee686/verl that referenced this pull request Jul 25, 2025
### What does this PR do?

bump main branch version to v0.5.0.dev

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here: ...
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`
oseyosey pushed a commit to oseyosey/verl that referenced this pull request Jul 28, 2025
### What does this PR do?

bump main branch version to v0.5.0.dev

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here: ...
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`
CurryRice233 added a commit to CurryRice233/verl that referenced this pull request Jul 28, 2025
* origin/mindspeed: (39 commits)
  [perf] feat: add optional role selection in discrete mode for NPU Profiler (volcengine#2750)
  [rollout] feat: remove chat scheduler (volcengine#2725)
  [trainer] refactor: Make sure to keep the type checking (volcengine#2634)
  [doc] style: change resize handle from gradient to plain color (volcengine#2746)
  [CI] feat: add `mypy` to pre-commit (volcengine#2614)
  [megatron] feat: a bunch of optimzation on vram, sequence packing (volcengine#2678)
  [docker] feat: upgrade to torch 2.7, sglang 0.4.8 (volcengine#2617)
  [doc] feat: add resizable sidebar and improve layout (volcengine#2577)
  [ci] fix: release ascend test time, fix one step off-policy CI (volcengine#2731)
  [recipe] chore: add retool training script (volcengine#2732)
  [ci] fix: checkpoint_convertor ci miss a hf model download (volcengine#2730)
  [doc] feat: Add agent-lightning in the list of "awesome works using verl (volcengine#2726)
  [tool] fix: geo3k create return str instead of tuple (volcengine#2714)
  [megatron] fix: resolve backward propagation error in megatron_actor due to shared logits tensor in-place modification (volcengine#2484)
  [misc] chore: bump main branch version to v0.5.0.dev (volcengine#2718)
  [sglang] fix: Adding strict naming sanity for sglang (volcengine#2719)
  [ray] feat: RayWorkerGroup support set worker env (volcengine#2685)
  [ci] test: add CriticWorker unit test, make some util CPU friendly (volcengine#2717)
  [cfg] refactor: add ActorConfig, EngineConfig, and ActorWorker unit test, refactor validation code (volcengine#2621)
  [misc] chore: bump version to v0.5.0 (volcengine#2716)
  ...
SumanthRH pushed a commit to SumanthRH/verl that referenced this pull request Jul 29, 2025
### What does this PR do?

bump main branch version to v0.5.0.dev

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here: ...
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`
Juniper1021 pushed a commit to Juniper1021/verl that referenced this pull request Aug 7, 2025
### What does this PR do?

bump main branch version to v0.5.0.dev

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here: ...
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`
whatadayG pushed a commit to whatadayG/verl that referenced this pull request Sep 5, 2025
### What does this PR do?

bump main branch version to v0.5.0.dev

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here: ...
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`
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