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

Release v2.10.3 #5581

Merged
merged 32 commits into from
Jan 6, 2021
Merged

Release v2.10.3 #5581

merged 32 commits into from
Jan 6, 2021

Conversation

jeremystretch
Copy link
Member

Bug Fixes

  • #5049 - Add check for LLDP neighbor chassis name to lldp_neighbors
  • #5301 - Fix misleading error when racking a device with invalid parameters
  • #5311 - Update child objects when a rack group is moved to a new site
  • #5518 - Fix persistent vertical scrollbar
  • #5533 - Fix bulk editing of objects with required custom fields
  • #5540 - Fix exception when viewing a provider with one or more tags assigned
  • #5543 - Fix rendering of config contexts with cluster assignment for devices
  • #5546 - Add custom field bulk edit support for cables, power panels, rack reservations, and virtual chassis
  • #5547 - Add custom field bulk import support for cables, power panels, rack reservations, and virtual chassis
  • #5551 - Restore missing import button on services list
  • #5557 - Fix VRF route target assignment via REST API
  • #5558 - Fix regex validation support for custom URL fields
  • #5563 - Fix power feed cable trace link
  • #5564 - Raise validation error if a power port template's allocated_draw exceeds its maximum_draw
  • #5569 - Ensure consistent labeling of interface mgmt_only field
  • #5573 - Report inconsistent values when migrating custom field data

jeremystretch and others added 30 commits December 21, 2020 16:19
Employ signals to update child objects when RackGroup/Rack site assignment changes
…els, rack reservations, and virtual chassis
…anels, rack reservations, and virtual chassis
Report inconsistent values when migrating custom field data
In the documentation the `ie` and `nie` filter expressions are
incorrectly marked as senstive matches when they are in fact
insensitive.
Fixes #5579: mark `ie` and `nie` filter exprs as insensitive
@jeremystretch jeremystretch merged commit 5a32b95 into master Jan 6, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants