# Query: Upgrade from v7 to v8

**URL:** <https://community.forestadmin.com/t/query-upgrade-from-v7-to-v8/6655>\
**Category:** Help me!\
**Created:** [September 13, 2023, 1:03pm UTC](https://community.forestadmin.com/t/query-upgrade-from-v7-to-v8/6655 "2023-09-13T13:03:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mukesh\_Bisht](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/mukesh_bisht/32/6315_2.png) [@Mukesh\_Bisht](https://community.forestadmin.com/u/Mukesh_Bisht)\
**Post date:** [September 13, 2023, 1:03pm UTC](https://community.forestadmin.com/t/query-upgrade-from-v7-to-v8/6655/1 "2023-09-13T13:03:43Z")

</div>

## Note: Nothing impacted till now i am just want to clarify things before migrating from v7 to v8.

## Feature(s) impacted

Scopes.

## Observed behavior

breaking change mentioned in doc [Upgrade to v8 | Developer Guide](https://docs.forestadmin.com/documentation/extra-help/maintain/upgrade-notes-sql-mongodb/upgrade-to-v8#breaking-changes)  
I am referering to above mentioned doc while stating my query  
screenshot for reference:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/7/70cf0b2c19733876ada6aa0546530850fba4447e.png)

## code which is closely relevant to the area of my concern.

## Main Query: i want to know that if i will upgrade my agent version for forest admin server from v7 to v8, then there is a possiblePreformatted text breaking change mentioned in doc [Upgrade to v8 | Developer Guide](https://docs.forestadmin.com/documentation/extra-help/maintain/upgrade-notes-sql-mongodb/upgrade-to-v8#breaking-changes) , whether scopes related breaking changes are only for permissionMiddlewareCreator.smartAction() or will they impact our code which is simple knex migration create related code :

code example:

```javascript
router.post('/knex_migrations_lock', permissionMiddlewareCreator.create(), (request, response, next) => {
 routes#create-a-record
  next();
});

```

supporting screenshot:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/d/dd16976c382da2b1441db8fd3b2e5cf3b3079f12.png)

## Context

- Project name: Blush Now
- Team name: blush now
- Environment name: My concern is related to all envs (as migration will be project level)
- Agent (forest package) name & version: forest-express-sequelize(want to go from v7 to v8)
- Database type: postgres (using sequelize orm)

---

<div class="post-metadata">

**Author:** ![anon34731316](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@anon34731316](https://community.forestadmin.com/u/anon34731316)\
**Post date:** [September 13, 2023, 3:39pm UTC](https://community.forestadmin.com/t/query-upgrade-from-v7-to-v8/6655/2 "2023-09-13T15:39:52Z")

</div>

Hello @Mukesh_Bisht,

Thanks for reaching out 🙌

I think I understood your question.  
To make it simple on the Scope breaking change: you need to check if you have any occurrence of `RecordsGetter` , `RecordCounter` , `RecordsExporter` , `RecordsRemover` , `RecordCreator` , `RecordGetter` , `RecordUpdater` , `RecordRemover` and `RecordsCounter`.  
If you do, then you need to change a bit their signature.  
If you don’t, you can ignore this change to make!

If you don’t use any smart action, you probably don’t use those methods indeed. But please double check, it won’t cost you a lot to verify.

Let me know if that helps.  
Cheers!

---

<div class="post-metadata">

**Author:** ![Mukesh\_Bisht](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/mukesh_bisht/32/6315_2.png) [@Mukesh\_Bisht](https://community.forestadmin.com/u/Mukesh_Bisht)\
**Post date:** [September 14, 2023, 5:19am UTC](https://community.forestadmin.com/t/query-upgrade-from-v7-to-v8/6655/3 "2023-09-14T05:19:37Z")

</div>

hi @anon34731316 thanks for your quick support.